Package: ntp Hi,
This problem exists on my freshly installed etch system as well. According to this link: https://ntp.isc.org/bugs/show_bug.cgi?id=129 the problem is as follows: When you startup the server needs to resolve the IP addresses in the config file. However, I run off an encrypted wireless link that doesn't startup till after I've logged in. The way ntp deals with this is to spawn a resolver process later to keep trying to resolve the name until it works. Unfortunatly, the default etch config file contains the following: # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 nomodify Which means the resolver process can't actually update the server with the new address. That's why restarting the server works, and probably why it works for most people. So the default etch configuration basically only works if DNS resolving works from the moment the system is started up. I'm playing with the config file to see what changes can be made to make it work. Have a nice day, -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to > litigate.
signature.asc
Description: Digital signature
