Date: Tue, 10 Dec 2002 01:20:03 -0800 (PST) From: "Sergey Amelyuschenko" <adminu5@mail.ru> To: freebsd-alpha@FreeBSD.org Subject: Re: alpha/45947: init does not invoke getty Message-ID: <200212100920.gBA9K3Sv052378@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR alpha/45947; it has been noted by GNATS. From: "Sergey Amelyuschenko" <adminu5@mail.ru> To: "Andrew Gallatin" <gallatin@cs.duke.edu> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: alpha/45947: init does not invoke getty Date: Tue, 10 Dec 2002 12:11:49 +0300 Hi Drew! > Hmm.. > > 2 ideas: > > 1) Perhaps it still thinks that its running a startup script and has not > made it fully multi-user. Have you installed or upgraded any ports > recently? something in /usr/local/etc/rc.d/foo.sh started so that it > does not go into the background might block init. > > > 2) init has gone totally insane. I'd stick some printfs > in transition_handler(), and in multi_user(), and in clean_ttys(). > So as to try to see what's happening when the signal is delivered. Wow! You are incredible! Your first idea was right! I had /usr/local/etc/rc.d/mysql-server.sh script hanging around from old version of mysql. This script did not go into the background during boot. Now I have upgraded mysql-server.sh and everything works as expected! Anyway, this experience raises the question of reliability of boot process. That is, by fooling around with /usr/local/etc/rc.d it is possible to prevent init from going multiuser. Is it possible to implement some anti-foot-shooting technique? I mean if script was not started in some timeframe just kill it and go on to the next one? Thanks again for your help! Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212100920.gBA9K3Sv052378>