Closing as the bug has not been reported since Feisty.
** Changed in: ntp (Ubuntu)
Status: Confirmed => Invalid
--
ntp daemon not reconfigured by /etc/network
https://bugs.launchpad.net/bugs/120199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
At this point I'm unsubscribing from the bug report. I no longer know,
or care, if the problem is still extant. Maybe it is and maybe it isn't,
but after a couple of years of the bug living in limbo I've ceased to
care, and I'm no longer running an Ubuntu laptop.
--
ntp daemon not reconfigured by
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
Hi Perry,
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 that restarting
the proc
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
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
- observe ntpd listening on the new address
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
The problem is present on:
- dapper: yes
- feisty: yes
- gutsy: no
- hardy: no
- intrepid: no
--
ntp daemon not reconfigured by /etc/network
https://bugs.launchpad.net/bugs/120199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
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
1) What version of Ubuntu was the bug reported on? Feisty?
2) Have you tested using the latest release of Ubuntu, Hardy Heron? This
has a newer version of ntp, which may have solved your problem.
3) Your bug description states that the solution is to remove certain
lines from certain files, but t
Hew McLachlan <[EMAIL PROTECTED]> writes:
> We are closing this bug report because it lacks the information we need
> to investigate the problem, as described in the previous comments.
I don't see what you are talking about. The information is all there.
> Please reopen it if you can give us the
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for your bug report. To maintain a respectful atmosphere,
please follow the code of conduct -
http://www.ubuntu.com/community/conduct/ . Bug reports are handled by
humans, the majority of whom are volunteers, so please bear this in
mind.
I noted that the files you mentioned a year ago do
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
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,
and from what I can tell, ntp works just fine. In addition, there have
been many changes to ntp since this bug was reported, so this is why we
ask that you
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
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. We were wondering is this still an issue
for you? The files you mentioned are not present in my testing with
Intrepid. Can you try
17 matches
Mail list logo
