[Bug 90267] Re: ntp starts before the network is up in feisty

[James]

Ntp seems to go out of it's way to not do a wildcard bind to port 123.
It is only binding to port 123 for each interface. If the interface is
not up it does not get bound to. This is from starting ntp after eth0 is
up.

Mar  9 06:36:46 fred ntpd[2276]: Listening on interface wildcard, 0.0.0.0#123 Disabled
Mar  9 06:36:46 fred ntpd[2276]: Listening on interface lo, 127.0.0.1#123 Enabled
Mar  9 06:36:46 fred ntpd[2276]: Listening on interface eth0, 172.16.31.2#123 Enabled

I started another machine and let it go for 30 minutes and no
difference. Ntp does not change.

Mar  9 07:52:34 wilma ntpd[5034]: ntpd 4.2.2p4 at 1.1585-o Wed Mar  7 20:43:30 UTC 2007 (1)
Mar  9 07:52:34 wilma ntpd[5035]: precision = 1.000 usec
Mar  9 07:52:34 wilma ntpd[5035]: Listening on interface wildcard, 0.0.0.0#123 Disabled
Mar  9 07:52:34 wilma ntpd[5035]: Listening on interface wildcard, ::#123 Disabled
Mar  9 07:52:34 wilma ntpd[5035]: Listening on interface lo, ::1#123 Enabled
Mar  9 07:52:34 wilma ntpd[5035]: Listening on interface lo, 127.0.0.1#123 Enabled
Mar  9 07:52:34 wilma ntpd[5035]: kernel time sync status 0040
Mar  9 07:52:34 wilma ntpd[5035]: frequency initialized -8.102 PPM from /var/lib/ntp/ntp.drift

By 8:22 no change.

-- 
ntp starts before the network is up in feisty
https://launchpad.net/bugs/90267