Your message dated Mon, 28 Jan 2008 19:55:11 +0100
with message-id <[EMAIL PROTECTED]>
and subject line [pkg-ntp-maintainers] Bug#462862: explain changes in ntp.conf
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ntp
Version: 1:4.2.4p4+dfsg-3
Severity: wishlist
When upgrading from dfsg-2 to dfsg-3 the default ntp.conf file has changed from
-------------------------
# pool.ntp.org maps to about 1000 low-stratum NTP servers.
# Your server will pick a different set every time it starts up.
# *** Please consider joining the pool! ***
# *** <http://www.pool.ntp.org/join.html> ***
# maxpoll works around a kernel bug in 2.6.18 and earlier
server 0.debian.pool.ntp.org iburst dynamic maxpoll 7
server 1.debian.pool.ntp.org iburst dynamic maxpoll 7
server 2.debian.pool.ntp.org iburst dynamic maxpoll 7
server 3.debian.pool.ntp.org iburst dynamic maxpoll 7
-------------------------------------------
to
--------------------------------------------
# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
server 0.debian.pool.ntp.org iburst dynamic
server 1.debian.pool.ntp.org iburst dynamic
server 2.debian.pool.ntp.org iburst dynamic
server 3.debian.pool.ntp.org iburst dynamic
-------------------------------------------------
The changes for which I need more information are the removal of
maxpoll and the associated comment.
It would be helpful to know if the change arises from an assumption
that the kernel will be > 2.6.18, or from some other fix. I have a
system that is still on 2.6.18, and I don't know if the new conf file
is safe for it.
I looked in the changed log and BTS, but couldn't find anything.
It would be useful to clarify the proper handling of 2.6.18 and
earlier kernels in the changelog, NEWS.Debian, the comments in
ntp.conf, or some combination.
Possibly this change was from some earlier version and I only picked
it up by running the diff. I do not think I amanually inserted the
lines shown above.
Thanks.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ntp depends on:
ii adduser 3.105 add and remove users and groups
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libreadline5 5.2-3 GNU readline and history libraries
ii libssl0.9.8 0.9.8g-3 SSL shared libraries
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii netbase 4.30 Basic TCP/IP networking system
Versions of packages ntp recommends:
ii perl 5.8.8-12 Larry Wall's Practical Extraction
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Jan 27, 2008 at 06:44:38PM -0500, Ross Boylan wrote:
> > I have no idea why you think any of this is related to a kernel version.
> > ntpd should be able to work with any kernel version.
> Well, the comment and the bug above report a problem with some kernel
> versions.
>
> Sorry: this is clearly a bogus wish, and would be OK to close. However,
> I'm still not sure what to do about the kernel timesync error. I think
> I'm seeing it periodically on 2.6.22 systems as well.
It seem there atleast were some bugs in the kernel. And some of them
got fixed.
Anyway, closing this bug as there is nothing we can do about it.
Kurt
--- End Message ---
