** Changed in: system-tools-backends (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83604
Title:
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed config
** Changed in: gst
Status: Unknown => Fix Released
** Changed in: gst
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83604
Title:
ntpdate 1:4.2.2.p4+dfsg-1ubu
** Changed in: system-tools-backends (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83604
Title:
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configurati
** Branch linked: lp:ubuntu/ntp
** Branch linked: lp:ubuntu/system-tools-backends
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83604
Title:
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configurat
This bug was fixed in the package system-tools-backends -
2.10.1-0ubuntu2
---
system-tools-backends (2.10.1-0ubuntu2) natty; urgency=low
* 03ubuntu_empty_ntp_conf.patch: Don't create empty NTP configuration
files (LP: #83604).
-- Colin WatsonMon, 06 Dec 2010 11:56:01 +
** Branch linked: lp:~ubuntu-desktop/system-tools-backends/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83604
Title:
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
--
ub
** Bug watch added: Debian Bug tracker #397648
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397648
** Also affects: system-tools-backends (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397648
Importance: Unknown
Status: Unknown
** Bug watch added: GNOME Bug Trac
This bug was fixed in the package ntp - 1:4.2.6.p2+dfsg-1ubuntu2
---
ntp (1:4.2.6.p2+dfsg-1ubuntu2) natty; urgency=low
* debian/ntpdate-debian: Disregard empty ntp.conf files (thanks, Mika
Wahlroos; LP: #83604).
* debian/ntp.preinst: Remove empty /etc/ntp.conf on fresh install
Mika, I'm dropping the debian/ntpdate.default part of your patch. It's
correct, and I agree that all other things being equal this
documentation should be brought up to date, but it's going to be very
common to have modified the NTPSERVERS line that immediately follows it
(or to be upgrading a sys
Mika's patch is certainly still applicable in Natty. I think I'm going
to go ahead and apply that; it seems common to have an empty
/etc/ntp.conf due to this (I had one myself) and this is an easy
workaround. There's a separate bug 427775 for more general logic
problems with /etc/network/if-up.d/
Is this still buggy in Lucid?
Anyway, I think fixing bug 583994 by replacing ntpdate with ntpd would
solve this the right way.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member of
The bug report for package "ntp" has been triaged and a priority
assigned. Only the package "system-tools-backends" has been marked
invalid as it does to appear to be the root cause of the problem
requiring a code fix.
(https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/83604/comments/15).
--
ntp
This bug still affects a fresh install of Jaunty, and it's left as
Invalid??? What am I missing?
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
The affected system-tools-backends package flags this bug as New and in need of
triage. Reading the comments suggests there is no fix required for this
package. I'll mark it as invalid for that reason, not because it is not
affected by the bug in ntp.
Should bug reports be raised against backen
** Changed in: ntp (Ubuntu)
Importance: Undecided => Medium
Status: Confirmed => Triaged
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Pedro,
That's a good catch. However, I don't suppose that change is going to
happen for hardy since ubuntu-minimal still seems to depend on ntpdate
in the current development branch. The time-admin package in hardy still
seems to generate an empty /etc/ntp.conf when the synchronize button is
press
As well, it is important to notice that ntpdate is deprecated upstream
and scheduled for deletion as stated in ntpd(8) in the entry for the -q
option, which is its functional replacement.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
Yo
Looks like it's actually quite easy to take the fallback option.
The attached patch makes ntpdate use /etc/ntp.conf only if it's readable
and non-empty. This fixes the breakage in case a tool has created an
empty configuration file for ntp.conf. The ntp configuration in
/etc/ntp.conf is still used
Now that I look at it, gnome-system-tools has hard depends on neither
ntpdate or ntp, but it suggests ntp. However, "suggests" doesn't make it
installed by default, and time-admin in gnome-system-tools remains
inoperative. It works if ntpdate works, though, even if the gnome-
system-tools package d
Basically, the problem is that with the default configuration ntpdate
only works if the ntp package is also installed (thus providing
/etc/ntp.conf), but while ntpdate is installed by default (ubuntu-
minimal depends on it), the ntp package is not (because nothing depends
on it, and it shouldn't re
Bah! I'm sleep-walking already! I meant
NTPDATE_USE_NTP_CONF=no
of course.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://launchpad.net/bugs/83604
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hmm... If erasing /etc/ntp.conf disables the "Synchronize Now" button in
time-admin, then the solution I offered in the original bug report seems
appropriate: Supply an /etc/default/ntpdate that sets:
NTPDATE_USE_NTP_CONF=yes
That works here.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed con
Ah. Now I understand why I just missed my bus!
"sudo rm /etc/ntp.conf" and it'll never happen again, hehe.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://launchpad.net/bugs/83604
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
BTW: as far as I can tell, this prevents the "Synchronize Now" button in
time-admin from working.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://launchpad.net/bugs/83604
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
On 2/7/07, Sebastien Bacher <[EMAIL PROTECTED]> wrote:
> didier, it's not clear why you opened that system-tools-backend, why do
> you think that's a bug on that package and not on ntp?
How to reproduce this bug:
On feisty
delete the empty /etc/ntp.conf if any
open from the panel or the control cen
didier, it's not clear why you opened that system-tools-backend, why do
you think that's a bug on that package and not on ntp?
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://launchpad.net/bugs/83604
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
I'm not sure for -s
With an empty /etc/ntp.conf ntpdate is not run at all because the set -e
in ntpdate-date script.
sh -x /usr/sbin/ntpdate-debian
set -e
+ [ -r /etc/default/ntpdate ]
+ . /etc/default/ntpdate
+ NTPDATE_USE_NTP_CONF=yes
+ NTPSERVERS=ntp.ubuntu.com
+ NTPOPTIONS=
+ [ yes = yes ]
He! You are right, it does (didn't see it earlier when I wrote the bug
report.)
Yet, syslog reporting is not working, because ntpdate-debian checks the
settings in /etc/default/ntpdate and acts accordingly. ntpdate should
log into /var/log/daemon.log (being exec'd as part the the init/upstart
proc
-s is set in /etc/network/if-up.d/ntpdate, isn't it?
Nope
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://launchpad.net/bugs/83604
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
-s is set in /etc/network/if-up.d/ntpdate, isn't it?
Not sure about 82774 too, AFAIK edgy doesn't use ntpdate-debian, just
plain ntpdate.
** Changed in: ntp (Ubuntu)
Status: Unconfirmed => Confirmed
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://launchpad.n
30 matches
Mail list logo
