[Info-vax] TCPIP tying up system

JF Mezei jfmezei.spamnot at vaxination.ca
Sun Nov 28 14:50:33 EST 2010


Henry Crun wrote:

> RBLs: zen.spamhaus.org
> to cut out a lot of spam.

This cuts spam, but doesn't prevent the SMTP receiver from bogging the
system down to a halt for normal users.

By the time it gets to process the RBL, all the overhead from process
creation, running a .COM, activating the .EXE, having it read its
config, accept the TCP connection etc has been spent.

When you set the service limit with TCPIP> SET SERVICE SMTP command, the
call is blocked by the TCP stack before the overhead of the TCP session
establishement is done (and well before process creation stuff is done).


The problem isn't a "crash dump", the problem is that the system gets to
100% use at high priority which prevents the system manager from taking
any action.

And pardon my ignorance here, doesn't "taking a crash dump"
imply/require that the system be crashed/shutdown/rebooted ? Or is it
possible to take a snapsghot of the running system with the system
continuing as normal once the snapshot has been taken ?





More information about the Info-vax mailing list