From owner-freebsd-stable Wed Dec 13 15: 9:42 2000 From owner-freebsd-stable@FreeBSD.ORG Wed Dec 13 15:09:37 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id C849C37B404 for ; Wed, 13 Dec 2000 15:09:36 -0800 (PST) Received: (qmail 69699 invoked from network); 13 Dec 2000 23:07:25 -0000 Received: from unknown (HELO telehouse.ch) ([195.134.128.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 13 Dec 2000 23:07:25 -0000 Message-ID: <3A380189.9B95A212@telehouse.ch> Date: Thu, 14 Dec 2000 00:08:57 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Mike Tancsa , hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: su root hangs when logged in via SSH References: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> <3A37E70C.3A935224@telehouse.ch> <200012132153.eBDLrn576602@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "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