Steve Langasek writes:
> I'm unclear about the meaning of your last message. How is ntp being
> told to aim at different NTP servers if you /do/ restart it? The
> default, static configuration shipped with the ntp package always points
> to ntp.ubuntu.com; how do you have ntp configured such th
mouz <[EMAIL PROTECTED]> writes:
> By 'the problem is not present' I mean the following:
> - prepare a KVM guest with the wanted release
> - install the ntp package on the guest
> - set the clock a minute backwards on the guest
> - force the network to change using the DHCP server on the KVM host
mouz <[EMAIL PROTECTED]> writes:
> The problem is present on:
> - dapper: yes
> - feisty: yes
> - gutsy: no
> - hardy: no
> - intrepid: no
What do you mean by "the problem is not present" -- what restarts ntpd
on gutsy or hardy? I still had this issue on Hardy when I last
checked -- I manually in
Pardon my frustration here. I feel as though I'm talking to a clerk at
the DMV who is insisting that my paperwork isn't in order. It is
starting to make me write in a manner that is perhaps more angry than
is appropriate, but it feels like I'm talking to a wall. The goal here
should not be to clos
Hew <[EMAIL PROTECTED]> writes:
> Your report states that there are problems with /etc/network/if-up.d/ntp
> and /etc/network/ntp-server, but these files do not exist in Intrepid,
The problem isn't those files. It is the functionality. The fact that
the files no longer exist at all might in fact
Hew <[EMAIL PROTECTED]> writes:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently.
That's not my fault. I reported a bug and no one bothered to try
fixing it. That doesn't m
