Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
> It was NOT ignored. If syslogd dies, then the system SHOULD stop, after a
Huh? "SHOULD"? Why? If syslog dies for any reason (bug, DOS, hack,
admin stupidity) then I sure don't want the system freezing up.
( heh... at work on Solaris I monitor 300+ systems, and it's not unusual
to find 1 box a week with syslog not running for some reason or another.
I can't decide whether it's admin stupidity or bugs in Solaris syslog - of
which there are many :-(( )
syslog is not meant to be a secure audit system. Messages can be
legitimately dropped. Applications have been coded assuming that they
will not be frozen in syslog(). Linux should not be different in this
respect. Hmm... it might be nice to be this a system tunable parameter
but I'm not sure the best way of doing that (glibc maybe?)
Stephen Harris
[EMAIL PROTECTED] 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.
* Mow ! 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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
Horst von Brand wrote:
> > > 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.
>
> Great! Yet another way in which root can get the rope to shoot herself in
> the foot. Anything _really_ new?
OK, let's go a step further - what if syslog dies or breaks in some way
shape or form so that the syslog() function blocks...?
My worry is the one that was originally raised but ignored: syslog() should
not BLOCK regardless of whether it's local or remote. syslog is not a
reliable mechanism and many programs have been written assuming they can
fire off syslog() calls without worry.
Stephen Harris
[EMAIL PROTECTED] 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.
* Mow ! 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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
Horst von Brand wrote: 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. Great! Yet another way in which root can get the rope to shoot herself in the foot. Anything _really_ new? OK, let's go a step further - what if syslog dies or breaks in some way shape or form so that the syslog() function blocks...? My worry is the one that was originally raised but ignored: syslog() should not BLOCK regardless of whether it's local or remote. syslog is not a reliable mechanism and many programs have been written assuming they can fire off syslog() calls without worry. Stephen Harris [EMAIL PROTECTED] 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. * Mow ! 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
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
[EMAIL PROTECTED] 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.
* Mow ! 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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
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 [EMAIL PROTECTED] 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. * Mow ! 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
