Date: Thu, 14 Dec 2000 00:08:57 +0100 From: Andre Oppermann <oppermann@telehouse.ch> To: "Louis A. Mamakos" <louie@TransSys.COM> Cc: Mike Tancsa <mike@sentex.net>, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: su root hangs when logged in via SSH Message-ID: <3A380189.9B95A212@telehouse.ch> References: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> <3A37E70C.3A935224@telehouse.ch> <200012132153.eBDLrn576602@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Louis A. Mamakos" wrote: > > > Mike Tancsa wrote: > > > > > > Yeah, I had a similar problem to this in the past where syslogd was kind of > > > hung, and the su was blocking waiting for I guess syslog to return. If you > > > can login as root on the console, kill syslogd, restart it and see if su > > > works once again. > > > > Nope, it does not work again. But after a couple of seconds after > > restarting syslogd I've got this messages on the console: > > "syslogd: timed out waiting for child" > > > > Another note, syslogd does not go with a normal kill, it needs a kill -9 > > to make it into heaven. > > > > Could this be related to having a serial console? > > This sounds very familiar to me. I had a problem like this in the > past, and it was a case of syslog blocking trying to write to /dev/console > and blocking. The comconsole port starts a getty on /dev/console, which > might be surprising if you also had one running on ttyd0. > > I don't recall the details, but I think that the serial console is > definately related to your problem. Yep, that seems to be the problem. As soon as I remove the getty it works. Interestingly enough syslogd doesn't matter at all, running or not it will not work as long as getty is active. Is there any work-around known? -- Andre 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?3A380189.9B95A212>