VERY Slow to start up when no network

Chanchao custom at freenet.de
Mon Jun 11 01:58:48 UTC 2007


On Fri, 2007-06-08 at 13:49 -0300, Derek Broughton wrote:

> > When no network connection is available, for example because I'm still
> > set to the company LAN but starting up at home to later join my home
> > wireless network, then the startup takes AGES.  Some things time out
> > causing a black screen with log messages,
> 
> That part seems normal - mine does it too as it seems to wait for the DHCP
> timeout on the network, even though it should know there _is_ no network.

For me it never took this long before.  The time it takes is really
exceptional; the system is unusable for about 5 minutes and error
messages appear on Gnome settings timing out.  I'm not using DHCP either
but even if I was, this can't be normal cannit..?    On laptops it
happens all the time that you're on a different network and need to
switch; this switching now easily takes 5 minutes before I can even get
the Network settings panel opened.

> > then finally I get to the 
> > login screen, but then again it takes forever for everything to come up,
> 
> _That_ sounds like 'lo' might not be up.  Do "ifconfig lo" and see what it
> says.  I had  a problem with that happening in Edgy, and never did figure
> out why.  I just put a script in /etc/init.d/ that did "ifconfig lo up" to
> work around it.

It says:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1485 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1485 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:78790 (76.9 KiB)  TX bytes:78790 (76.9 KiB)

However this is now after I got my network settings switched to my
company LAN. I will try it again when booting up without network.

> I have a different, but possibly similar, problem with KMail, which doesn't
> behave well when offline.  It seems to be related to the network-status
> daemon (there's a bug report somewhere on launchpad).  Konqueror also
> doesn't work with "localhost" addresses when you're offline (but firefox
> does).  Look back through the archive for my question about konqueror and
> localhost - there's a link to the bug report in a response to that.

Thanks!!! All very helpful, I'll check it out.

Cheers,
Chanchao





More information about the ubuntu-users mailing list