From owner-freebsd-questions Fri Jun 28 11:10:58 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18886 for questions-outgoing; Fri, 28 Jun 1996 11:10:58 -0700 (PDT) Received: from mail.Clark.Net (mail.clark.net [168.143.0.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18881 for ; Fri, 28 Jun 1996 11:10:55 -0700 (PDT) Received: from clark.net (root@clark.net [168.143.0.7]) by mail.Clark.Net (8.7.3/8.6.5) with ESMTP id OAA24813; Fri, 28 Jun 1996 14:10:47 -0400 (EDT) Received: from clark.net (markus@localhost [127.0.0.1]) by clark.net (8.7.1/8.7.1) with ESMTP id OAA14224; Fri, 28 Jun 1996 14:10:45 -0400 (EDT) Message-Id: <199606281810.OAA14224@clark.net> To: "Jordyn A. Buchanan" cc: freebsd-questions@freebsd.org Subject: Re: Slow booting In-reply-to: Your message of "Fri, 28 Jun 1996 11:37:29 EDT." <2.2.32.19960628153729.00679b90@pop.bestweb.net> Date: Fri, 28 Jun 1996 14:10:44 -0400 From: Mark Plummer Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hello: > > One of our machines is stalling as it boots. Not stalling, really but > pausing for about five minutes before moving on. Here's what I see: > > >lo0: flags=8009 mtu 16384 > > inet 127.0.0.1 netmask 0xff000000 > >ed1: flags=8863 mtu 1500 > > inet 192.168.1.15 netmask 0xffffff00 broadcast 192.168.1.255 > > ether 00:40:33:3b:d8:1d > ---THIS IS WHERE THE DELAY OCCURS--- > >clearing /tmp > > Initially I had thought something in the static routes might be causing the > hang, but I took those out and the problem persists. I have two other > systems with the exact same NE2000-compatible networking card on almost the > exact same configuration (the others have slightly more RAM and use SCSI > instead of IDE drives) so I haven't a clue what's causing the problem. > > If I hit control-C while the system is paused, the boot will continue > normally, and I don't notice any adverse effects. Obviously, some idea of > what is causing the boot process to hang would be better than needing to > manually abort something every time, though. (And I'd rather know what I > was aborting too.) > > Thanks for your help, > > Jordyn > > P.S. We're testing this system behind a firewall before we get our actual > 'Net feed next month, hence the 192.168. network numbers... > > check and see if you're using names to refer to hosts or nets and if so, if your dns (or yp) is configured yet (yet == at the hanging point of the boot). i don't like to use names for sysconfig since they're not always translatable early in the boot process... markus -- Mark Plummer, markus@clark.net, +1 410 796 1272