George Deka george.deka at gmail.com
Tue Nov 15 07:12:59 CST 2005


>
>
>
> I think we can leave ntpdate where it is, but make the script smarter
> and check if we have an interface up that's likely to provide internet
> access (i.e. ethX, whatever the wireless interfaces are called).
>
> For dhcp, there are two options that we should investigate. If you take
> a look at the dhclient.conf man page, you see that you can specify a
> specific timeout. The default is 60 seconds, any reasonable dhcp server
> will respond much faster then that. I don't think cutting that down to
> 30, or even less would be unreasonable. Also, dhclient has a flag
> '-nw'. This forces it to go straight to daemon mode without waiting for
> an ip address however this is problematic for network dependend services
> that come after.
>
> Proposal

move dhcp discovery to as early in the boot process as possible and call it
with -nw so it tries to get a ip in the background.
Then leave ntp to the last of the boot items, that way you should have
secured a ip in that time, also maybe look into reducing the ntp timeout.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ubuntu.com/archives/ubuntu-devel/attachments/20051116/1c4cf870/attachment-0001.htm


More information about the ubuntu-devel mailing list