A lot of talk here has been about syslog and DNS blocking, but the
original message mentioned:
> If you send SIGSTOP to syslogd on a Red Hat 6.2 system (glibc 2.1.3,
> kernel 2.2.x), within a few minutes you will find your entire machine
> grinds to a halt. For example, nobody can log in.
Has this been addressed (and I missed it) or did the question get
diverted? If it has been addressed, just please mail me personally to
save traffic on the list.
Thanks!
-- Stephen Harris sweh@spuddy.mew.co.uk http://www.spuddy.org/ The truth is the truth, and opinion just opinion. But what is what? My employer pays to ignore my opinions; you get to do it for free. * Meeeeow ! Call Spud the Cat on > 01708 442043 < for free Usenet access * - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 31 2000 - 21:00:23 EST