On Tue, 2006-02-21 at 16:15 -0600, Darryl Gregorash wrote:
On 21/02/06 14:25, Roger Oberholtzer wrote:
Anyone else have difficulty using this on boot when the network gets started via DHCP? What I 'think' is happening is that the ntp daemon does not start properly since the network is not yet functional, and never recovers when the DHCP completes. Anyone else have issues with ntp starting properly on boot? Check these:
/etc/sysconfig/network/config -->
## Type: integer ## Default: 20 # # Some interfaces need some time to come up or come asynchronously via hotplug. # WAIT_FOR_INTERFACES is a global wait for all mandatory interfaces in # seconds. If empty no wait occurs. # WAIT_FOR_INTERFACES="20"
and also /etc/sysconfig/network/dhcp -->
## Type: integer ## Default: 0 # # Some interfaces need time to initialize. Add the latency time in seconds # so these can be handled properly. Should probably set per interface rather than here. # DHCLIENT_SLEEP="0"
## Type: integer ## Default: 5 # # When the DHCP client is started at boot time, the boot process will stop # until the interface is successfully configured, but at most for # DHCLIENT_WAIT_AT_BOOT seconds. # DHCLIENT_WAIT_AT_BOOT="5"
My settings are these, which must be the default. It seems a hack to just wait a certain amount of time. My wireless goes through an access point that seems to take various amounts of time to respond to dhcp requests. I would expect a flag that tells when an interface is fully configured. Is this timeout the only way? I see that the system does count down 20 (from WAIT_FOR_INTERFACES I guess) when setting up the interfaces. I will extend this and see what I get. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23