and... yes indeed. Per chance I had started my laptop with a wireless connection, driven by n-m.
Here's the NTP messages for the startup: Mar 8 18:28:00 localhost ntpd[8566]: ntpd [EMAIL PROTECTED] Wed Mar 7 20:43:39 UTC 2007 (1) Mar 8 18:28:00 localhost ntpd[8567]: precision = 1.000 usec Mar 8 18:28:00 localhost ntpd[8567]: Listening on interface wildcard, 0.0.0.0#123 Disabled Mar 8 18:28:00 localhost ntpd[8567]: Listening on interface wildcard, ::#123 Disabled Mar 8 18:28:00 localhost ntpd[8567]: Listening on interface lo, ::1#123 Enabled Mar 8 18:28:00 localhost ntpd[8567]: Listening on interface lo, 127.0.0.1#123 Enabled Mar 8 18:28:00 localhost ntpd[8567]: kernel time sync status 0040 Mar 8 18:28:00 localhost ntpd[8567]: frequency initialized 12.637 PPM from /var/lib/ntp/ntp.drift Mar 8 18:28:00 localhost ntpd[8575]: signal_no_reset: signal 17 had flags 4000000 Mar 8 18:28:02 localhost ntpd_initres[8575]: host name not found: ntp.ubuntu.com Mar 8 18:28:02 localhost ntpd_initres[8575]: couldn't resolve `ntp.ubuntu.com', giving up on it Mar 8 18:28:02 localhost ntpd_initres[8575]: host name not found: pool.ntp.org Mar 8 18:28:02 localhost ntpd_initres[8575]: couldn't resolve `pool.ntp.org', giving up on it Mar 8 18:33:55 localhost ntpdate[9707]: the NTP socket is in use, exiting Mar 8 20:33:33 localhost ntpd[8567]: ntpd exiting on signal 15 So we have the interfaces disabled, everywhere. NTP is up, but is just wasting CPU cycles and memory. The errors on name resolution are expected, since I do not have a caching NS running on my laptop. Would not help much, anyways :-) So I restarted it, now with the wireless running: Mar 8 20:33:36 localhost ntpd[14447]: ntpd [EMAIL PROTECTED] Wed Mar 7 20:43:39 UTC 2007 (1) Mar 8 20:33:36 localhost ntpd[14448]: precision = 1.000 usec Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface wildcard, 0.0.0.0#123 Disabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface wildcard, ::#123 Disabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface vmnet8, fe80::250:56ff:fec0:8#123 Enabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface lo, ::1#123 Enabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface eth1, fe80::290:4bff:feff:c508#123 Enabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface lo, 127.0.0.1#123 Enabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface eth1, 192.168.1.3#123 Enabled Mar 8 20:33:36 localhost ntpd[14448]: Listening on interface vmnet8, 192.168.54.1#123 Enabled Mar 8 20:33:36 localhost ntpd[14448]: kernel time sync status 0040 Mar 8 20:33:36 localhost ntpd[14448]: frequency initialized 12.637 PPM from /var/lib/ntp/ntp.drift and my wireless interface, eth1, is now being used by NTP. Hum. I will have to munch a bit on this. Your comments will be appreciated. -- ntp starts before the network is up in feisty https://launchpad.net/bugs/90267 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
