reopen 561622 reassign 561622 ntp found 561622 1:4.2.4p4+dfsg-8lenny3 thanks
On 13/06/13 01:30, Carl Mascott wrote: > Bug 56122: Original bug report misunderstood; root problem not corrected Back in 2009, the bug was assigned to libnss-mdns. Kurt Roeckx recommended a change to /etc/nsswitch.conf. While updating libnss-mdns I made that change to nsswitch.conf for new installations. Please try removing "mdns4" from the end of the hosts line in nsswitch.conf (equivalent to the change I made in libnss-mdns 0.10-4). If that change to nsswitch.conf does not solve your problem then I can't do anything more for this from libnss-mdns' point of view; reassigning back to ntp. > No network service should be started until NetworkManager indicates that > the network interface is up. This is not practical to achieve in a world where networking is not 100% reliable (i.e. wifi and mobile broadband exist) - a machine should not fail to boot because it can't get on a network. > It is impractical to try to bulletproof every network service to deal > with the network interface being down when the service tries to start. On my laptop, it appears that ntpd does respond to changes in connectivity: Jun 13 11:45:07 archetype NetworkManager[1370]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. ... Jun 13 11:45:07 archetype dhclient: bound to x.x.x.194 -- renewal in 18564 seconds. ... Jun 13 11:45:11 archetype ntpd[1697]: Listen normally on 13 wlan0 x.x.x.194 UDP 123 Jun 13 11:45:11 archetype ntpd[1697]: Listen normally on 14 wlan0 fe80::x:x:x:x UDP 123 Jun 13 11:45:11 archetype ntpd[1697]: peers refreshed so this may in fact already be solved. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org