I know it's a long time, but I'm cleaning up old NTP bugs atm.
We haven't had any similar reports since then and popularity of nis declined
since then.
Also even basic time is - without further conf - handled by systemd now which
has totally different dependencies for all of this.
Finally this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/999725
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999725
Title:
broken
I'm currently troubleshooting a problem with a Lubuntu Quantal setup
with LTSP (terminal server network).
Most of the clients stop responding at a blank/black screen during
bootup. But only after successfully PXE network booting, getting DHCP
assignments, and beginning the process of booting
@John: Does the affected machine have nis on the hosts line in
/etc/nsswitch.conf? If not then your problem is not the same as this
one.
** Changed in: ntp (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
No, nis is not on hosts line of nsswitch.conf. I agree that my case is
not the same as the one reported.
But since the problem here is reported to be one in which ntp is being
started before the system is capable of resolving DNS, I couldn't help
but notice the similarity to my previous problem
I'm currently troubleshooting a problem with a Lubuntu Quantal setup
with LTSP (terminal server network).
Most of the clients stop responding at a blank/black screen during
bootup. But only after successfully PXE network booting, getting DHCP
assignments, and beginning the process of booting
@John: Does the affected machine have nis on the hosts line in
/etc/nsswitch.conf? If not then your problem is not the same as this
one.
** Changed in: ntp (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
No, nis is not on hosts line of nsswitch.conf. I agree that my case is
not the same as the one reported.
But since the problem here is reported to be one in which ntp is being
started before the system is capable of resolving DNS, I couldn't help
but notice the similarity to my previous problem
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ntp (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ntp (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999725
Title:
It is probably true that this has not been seen much as a bug due to DNS
normally being available, hence NIS dependency (if present) being a
secondary issue. However, we found that ntp did not recover by itself,
so possibly it only tries to find the nameservers once, but will re-try
for the time
It is probably true that this has not been seen much as a bug due to DNS
normally being available, hence NIS dependency (if present) being a
secondary issue. However, we found that ntp did not recover by itself,
so possibly it only tries to find the nameservers once, but will re-try
for the time
I'm not sure off hand how the decision is made whether to
convert a package such as ntp to Upstart... but I see a
couple other bugs open on the topic: LP #604717 , LP #913379
Sorry, should have written those bug references as: LP: #604717 , LP:
#913379
--
You received this bug notification
I'm not sure off hand how the decision is made whether to
convert a package such as ntp to Upstart... but I see a
couple other bugs open on the topic: LP #604717 , LP #913379
Sorry, should have written those bug references as: LP: #604717 , LP:
#913379
--
You received this bug notification
15 matches
Mail list logo
