From: sweh@spuddy.mew.co.uk (Stephen Harris)
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Subject: Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
Date: Sat, 28 Oct 2000 19:36:00 GMT [thread overview]
Message-ID: <G35ns0.3rD@spuddy.mew.co.uk> (raw)
In-Reply-To: <G31psL.73r@spuddy.mew.co.uk>
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/
next parent reply other threads:[~2000-10-28 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <G31psL.73r@spuddy.mew.co.uk>
2000-10-28 19:36 ` Stephen Harris [this message]
2000-10-28 23:51 ` syslog() blocks on glibc 2.1.3 with kernel 2.2.x Horst von Brand
2000-10-29 9:20 ` Stephen Harris
2000-10-29 16:35 ` Jesse Pollard
2000-10-29 17:18 ` Stephen Harris
2000-10-30 0:45 ` Igmar Palsenberg
2000-10-30 14:17 ` Jesse Pollard
2000-10-29 18:48 ` James Sutherland
2000-10-30 14:06 ` Jesse Pollard
[not found] <Pine.LNX.4.04.10010261143060.14708-100000@beaker.bluetopia.net>
2000-10-27 22:15 ` Igmar Palsenberg
[not found] <s5gy9zbzkz3.fsf@egghead.curl.com>
2000-10-27 22:10 ` Igmar Palsenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=G35ns0.3rD@spuddy.mew.co.uk \
--to=sweh@spuddy.mew.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).