Date: Sun, 30 Dec 2001 13:59:03 -0500 (EST) From: Brian McDonald <brian@lustygrapes.net> To: David Malone <dwmalone@maths.tcd.ie> Cc: Chris Johnson <cjohnson@palomine.net>, <stable@FreeBSD.ORG> Subject: Re: syslogd blocking => can't su to root Message-ID: <20011230133123.W2949-100000@nivomede.internal.lustygrapes.net> In-Reply-To: <20011230173548.A58662@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
The boxes I've noticed this on are 4.1-RELEASE boxes. Kernel configs are essentially GENERIC with devices removed that aren't present on the system (eisa, scsi cards, net cards, etc). Both have IPFIREWALL. One runs named and sshd, the other runs named, sshd, and postfix. At the time of the failures, both ran syslogd with the -s argument. Nothing really out of the ordinary except for the fact that both have been running for a year and half straight. (okay, on BSD that isn't out of the ordinary.) Both are hooked up to a Belkin KVM - can a twitchy ps2 mouse/keyboard irritate the console driver? Twice in a year isn't exactly 'easily reproducible', so I didn't bother really digging into it, until I saw that someone else noted it as well. If it happens again, I'll try to collect more information and open a PR. Brian On Sun, 30 Dec 2001, David Malone wrote: > Date: Sun, 30 Dec 2001 17:35:48 +0000 > From: David Malone <dwmalone@maths.tcd.ie> > To: Brian McDonald <brian@lustygrapes.net> > Cc: Chris Johnson <cjohnson@palomine.net>, stable@FreeBSD.ORG > Subject: Re: syslogd blocking => can't su to root > > On Sun, Dec 30, 2001 at 11:30:54AM -0500, Brian McDonald wrote: > > I've seen this on 4.1-RELEASE boxes as well. Was hoping it would just go > > away when I upgrade them to 4.5. I noticed it when it blocked other > > processes waiting for syslog, such as named. > > To fix this there we'd have to decide what should happen when syslogd > finds that some destination for messages becomes blocking. Syslogd > could just drop messages which would cause blocking. Alternatively, > syslogd could allow a certain amount of backup for which it would > buffer. > > Also, it is bad that syslogd can stop other processes by not reading > from its socket - it's possible we should change syslog(3) to timeout > or not to block. > > Have you noticed what causes your systlogd to get backed up? I've > never seen it happen on any of the machines I look after, so maybe > you have some unusual configuration which makes you prone to it? > > David. > > -- Brian McDonald, MCP Klein bottle for sale. Inquire within. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011230133123.W2949-100000>