Hi, Yes thats the whole problem! The no-association IDs is caused by ntpd coming up too early - a restart fixes this. What the fix does is PRIOR to S23ntp running ntpd will not be started due to the if-up script - this means that subsequently when S23ntp runs S15bind9 has already come up and therefore addresses on a local DNS based server will resolve.
Testing shows this works a treat and doesnt interfere with my laptop's wireless card connection either. The test about ntpd running is merely to determine whether or not to use the init.d script and restart. If its not running you wont get 'no association IDs' - you will get 'connection refused' when using ntpq. Hope this helps, Barry J Carerra wrote: > RE: the previous three... > > hmmmm...I am sure I have seen cases where ntpd is running, but no > associations are active; therefore, I am not sure that just testing if > ntpd is running fully covers all possible cases.. > > -- Sincerely Yours Copyright Witness Net Support [EMAIL PROTECTED] www.copyrightwitness.com Registration centre for copyright works. This e-mail and any attachments are confidential and intended for the addressee only. The information in this mail does not amount to legal advice or opinion. Any views or legal references are those of the author and are based on personal opinion or understanding only. -- ntp brought up before network is ready; fails not resolve any ip or host names; ntp does not recover https://bugs.launchpad.net/bugs/114505 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
