Date: Sun, 6 Jan 2002 14:48:04 -0500 From: Chris Johnson <cjohnson@palomine.net> To: David Malone <dwmalone@maths.tcd.ie> Cc: stable@FreeBSD.ORG Subject: Re: syslogd blocking => can't su to root Message-ID: <20020106144804.A91344@palomine.net> In-Reply-To: <20020106171717.A5758@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Sun, Jan 06, 2002 at 05:17:17PM %2B0000 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> <20020106171717.A5758@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
--x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 06, 2002 at 05:17:17PM +0000, David Malone wrote: > 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. > >=20 > > That's the case in my situation. The box is running just fine, providin= g all o > > the services it always does. I just can't su to root, because syslogd c= an't > > write "su to root," or whatever it says, on the console. >=20 > 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. >=20 > (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.) >=20 > PR 8865 might be related to this. I wonder if the gap in Chris's > logs started just after syslogd would have been HUPed? >=20 > 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. The problem was caused by someone inadvertantly scroll-locking the terminal. Once it was un-scroll-locked, the problem vanished. Chris --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8OKnvyeUEMvtGLWERAq0yAJ46YGidF2sx9tZIdBZTevqQfh6BuQCguQro 7sQvQQnouf0c3uD/I40xTcM= =DGoe -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- 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?20020106144804.A91344>