I am having a problem with ntp being started before the dhcp client has brought up the network. The end result is a non working ntp. /var/log/daemon.log shows
network manager starting
ntp starts but can only bind to lo because eth0 is not up yet
network manager then brings up eth0 via dhcp
ntpdate is run which fails because ntp is running
If I /etc/init.d/ntp restart after the machine has booted ntp works fine.
I am not familiar with the way the bootscripts are controlled in ubuntu. The best I can think of is see what a sleep 5 does at the start of /etc/init.d/ntp (if parallel start up) or putting /etc/init.d/ntp restart in rc.local. Both of which are crude.
What would I look for to see why ntp is being started before the network is brought up?
network manager starting
ntp starts but can only bind to lo because eth0 is not up yet
network manager then brings up eth0 via dhcp
ntpdate is run which fails because ntp is running
If I /etc/init.d/ntp restart after the machine has booted ntp works fine.
I am not familiar with the way the bootscripts are controlled in ubuntu. The best I can think of is see what a sleep 5 does at the start of /etc/init.d/ntp (if parallel start up) or putting /etc/init.d/ntp restart in rc.local. Both of which are crude.
What would I look for to see why ntp is being started before the network is brought up?
Comment