Since Gutsy is no longer supported. I am going to set this as wont fix.
If you can reproduce this on hardy please re-open the bug.
Thanks
chuck
** Changed in: ntp (Ubuntu)
Status: Confirmed => Won't Fix
--
Ntp doesn't synchronise on startup in Gutsy
https://bugs.launchpad.net/bugs/158110
I'm seeing a similar problem to this on one of my developer machines.
Here's what seems to be the startup order:
Network is configured, except for the interface listed as "roaming"
ntpd starts, fails to resolve server names, finds nowhere to sync to
roaming interface gets a dhcp address
ntpdate tr
ntpdate should not hold on to the port after it's completed updating the
clock, so starting ntpdate before ntpd should not be a problem as long
as ntpdate has completed its update. If it is, then we have a buggy
ntpdate. I have seen other Linux distributions do this with no problems
at all in getti
>The log file shows ntp is started before ntpdate. Therefore, when ntpdate gets
>started, the ntp socket is already in use, ntpdate fails and the clock can not
>be corrected immediately. I can reproduce this on my own Gutsy system, when
>roaming mode is used.
>This looks like ntp should be start
I can confirm it as well.
--
Ntp doesn't synchronise on startup in Gutsy
https://bugs.launchpad.net/bugs/158110
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
OK, Thanks for your help!
Could I change anything now or should I wait for an update?
Bye,
Ruben
albert wrote:
> >From the log file:
> Oct 30 06:32:01 rubuntu ntpd[5211]: ntpd [EMAIL PROTECTED] Thu Oct 4 20:58:45
> UTC 2007 (1)
> Oct 30 06:33:45 rubuntu ntpdate[6183]: the NTP socket is in use, ex
>From the log file:
Oct 30 06:32:01 rubuntu ntpd[5211]: ntpd [EMAIL PROTECTED] Thu Oct 4 20:58:45
UTC 2007 (1)
Oct 30 06:33:45 rubuntu ntpdate[6183]: the NTP socket is in use, exiting
The log file shows ntp is started before ntpdate. Therefore, when ntpdate gets
started, the ntp socket is alread
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Do you use dhcp to get an IP address for your network connection?
* Can you please attach the file /var/log/syslog? Please make sure the syslog
includes a reboot.
This will help u
