network services at boot (was Re: Boot charting)

On Mon, Nov 14, 2005 at 08:45:20AM +0000, Matthew East wrote:
> On Sun, 2005-11-13 at 18:02 +0000, Matthew East wrote:
> > On Sun, 2005-11-13 at 18:27 +0100, Oliver Grawert wrote:
> > > hi,
> > > On So, 2005-11-13 at 16:10 +0000, Matthew East wrote:
> 
> > To be honest I am actually quite pleased with boot times (45 seconds is
> > fine for me, and since suspend to ram works too...), the only thing that
> > really constitutes a problem is the fact that the network ifup service
> > stops for ages while I am not within range of my home network (for
> > example if I move to the office) and this then leads to the ntpdate
> > service losing lots of time too. I use profiles in network-admin, but of
> > course this doesn't help on boot.
> > 
> > On Windows, one of the reasons it is quicker at booting is (I think)
> > that it doesn't hang around waiting for the network services to start
> > up. Then again, it takes a hell of a lot longer to log in on Windows
> > than to log into Gnome. :)
> 
> Idea: would it be possible to remove the ntpdate service from startup
> altogether? I've noticed that update-manager manages to reload my apt
> sources in the background after I've entered my password for other
> administrative services, perhaps it could be taught to update the clock
> from the internet via ntpdate too? Users should be able to disable that
> from the Time & Date administrative tool.
> 
> This to me would make more sense than running it at boot when loads of
> people don't have the internet up. In many cases, the ntpdate services
> doesn't fail quickly: it can keep searching for ages!
> 
> Probably this idea has occurred to you guys before and you've rejected
> it for some reason, if so, please ignore me. But I think on the face of
> things it would be a sensible solution.

Yes, I have suggested this, it has been rejected by others saying that
we should ntp at boot to make sure th edate is correct for files being
setup etc. (most times dates are wrong, its slow, so bringing the date
forward is not a problem, the only ever issue is putting dates back,
which causes some 'too new' errors, i think the odd case this might
happen is not worth making the boot time of half of ubuntus users 30s
longer worth it)

Personally, I see NTP sit therre for 30-60 seconds far too often and I
think that is totally unacceptable.

DHCP is another culprit, we really need some kind of dependancy thing so
that gdm etc can start while DHCP is still starting.

But yeh, NTP is a killer and lots of people i know personally complain
about it

Trent

> 
> Matt
> -- 
> mdke at ubuntu.com
> gnupg pub 1024D/0E6B06FF



> -- 
> ubuntu-devel mailing list
> ubuntu-devel at lists.ubuntu.com
> http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel


-- 
Trent Lloyd <lathiat at bur.st>
Bur.st Networking Inc.