From owner-freebsd-alpha Tue Dec 10 5:52:16 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D462437B404 for ; Tue, 10 Dec 2002 05:52:14 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D7543EB2 for ; Tue, 10 Dec 2002 05:52:10 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA20337; Tue, 10 Dec 2002 08:52:04 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gBADpYG04318; Tue, 10 Dec 2002 08:51:34 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15861.61798.819616.443906@grasshopper.cs.duke.edu> Date: Tue, 10 Dec 2002 08:51:34 -0500 (EST) To: "Sergey Amelyuschenko" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: alpha/45947: init does not invoke getty In-Reply-To: <200212100920.gBA9K3Sv052378@freefall.freebsd.org> References: <200212100920.gBA9K3Sv052378@freefall.freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sergey Amelyuschenko writes: > > 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! Whew. I'm glad that's all it was. > 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? I have no idea. Its a little outside the scope of what I'm interested in. You might try proposing something like this in a more general mailing list (freebsd-arch, freebsd-hackers).. > Thanks again for your help! You're welcome. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message