Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Jan 2002 17:17:17 +0000
From:      David Malone <dwmalone@maths.tcd.ie>
To:        Chris Johnson <cjohnson@palomine.net>
Cc:        stable@FreeBSD.ORG
Subject:   Re: syslogd blocking => can't su to root
Message-ID:  <20020106171717.A5758@walton.maths.tcd.ie>
In-Reply-To: <20011230184545.A6319@palomine.net>; from cjohnson@palomine.net on Sun, Dec 30, 2001 at 06:45:46PM -0500
References:  <20011230081106.A98698@palomine.net> <20011230111949.G2732-100000@nivomede.internal.lustygrapes.net> <20011230173548.A58662@walton.maths.tcd.ie> <20011230215027.A62327@walton.maths.tcd.ie> <20011230184545.A6319@palomine.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 30, 2001 at 06:45:46PM -0500, Chris Johnson wrote:
> > There is actually a comment saying "don't worry about blocking; if
> > the console blocks everything will". This doesn't seem to be true
> > if network services could keep running.
> 
> That's the case in my situation. The box is running just fine, providing all o
> the services it always does. I just can't su to root, because syslogd can't
> write "su to root," or whatever it says, on the console.

I've checked a bit more carefully, and I think syslod(3) should
definitely be changed to not block. The interesting thing is that
syslogd seems to be written to avoid blocking while writing to ttys,
so I can't figure out how it is getting into the ttywai state.

(What is supposed to happen is that is syslogd is writing to a tty
then it uses ttymsg. Ttymsg forks and waits for a few seconds if
the write would block.)

PR 8865 might be related to this. I wonder if the gap in Chris's
logs started just after syslogd would have been HUPed?

If Chris or Brian can get a core from a hung syslogd (with kill -6)
I'd love to have a look at it and find out how it's managing to get
into that state.

	David.

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?20020106171717.A5758>