From owner-freebsd-hackers Wed Jun 28 09:58:38 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA13108 for hackers-outgoing; Wed, 28 Jun 1995 09:58:38 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA13102 for ; Wed, 28 Jun 1995 09:58:35 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA09811; Wed, 28 Jun 1995 09:57:42 -0700 From: "Rodney W. Grimes" Message-Id: <199506281657.JAA09811@gndrsh.aac.dev.com> Subject: Re: hanging boot To: jhs@vector.eikon.e-technik.tu-muenchen.de (Julian Howard Stacey) Date: Wed, 28 Jun 1995 09:57:42 -0700 (PDT) Cc: hackers@freebsd.org In-Reply-To: <199506271250.OAA00707@vector.eikon.e-technik.tu-muenchen.de> from "Julian Howard Stacey" at Jun 27, 95 02:50:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1872 Sender: hackers-owner@freebsd.org Precedence: bulk > > I've just seen my system appear to hang on boot > (at a similar point a friend's machine (me@freebsd.org) > did a couple of weeks ago) > it's a fresh install of 2.0.5 rel. on previously proven hardware, > > The problem is that I scattered the ether number of my master freebsd box in > too many places on the new box while installing, & now the new box > is hanging waiting for name server etc that the old box is not running. > It's currently hanging for a few minutes on each line of > add net default: gateway 134.98.91.21 > add net 224.0.0.0: gateway lion, > starting routing daemons: routed > When it finally boots the whole way, I'll fix my /etc/ files > > Thing is newbies may do this too, see the thing hang, & not know what the > problem is, & reset. > > Perhaps after "Automatic reboot in progress" > we should on a virgin fresh release have in /etc/rc something like: > echo "If this appears to hang, leave it for a half hour, then look > again, in case your net config is bad & needs to time out" I wouldn't go that far, but I do think we need a few more echo's in the rc scripts so that these hangs can be more accurately pin pointed by the last line of output on the console. My new version of the /etc/rc* stuff is only slighly more verbose than the current version. I will look at adding more verbosity (and with a rc_verbose knob, default ON, in sysconfig) to the startup. Thanks for reminding me of this, as I have hung and/or gotten errors there due to massive reconfigs of the aac.dev.com networking in the past and had forgotten how missleading it can be as to what is wrong. There are no less than 5 places that lots of things are done in /etc/rc* without *ANY* output. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD