I have just found that following the upgrade to sarge, ntpd segfaults
on boot. I happened to mention this in a local irc channel, and one
of my users mentioned that they had reported it as a bug. So I went
and looked at the Debian bugs logs.
I have determined that:
* my ntpd segfaults on startup if any hostname with an aaaa record is
listed in the ntpd.conf
* my ntpd does not segfault on startup otherwise.
* this bug seems to have been present for well over a year and
has been reported numerous times by other users
* the bug is described upstream at
https://ntp.isc.org/bugs/show_bug.cgi?id=353
* upstream are using BitKeeper (spit) so it is virtually impossible
for a normal Free Software developer to separate out the relevant
patch
* The Debian package was made from a random snapshot of upstream ntp.
Note that `4.2.0a' does NOT uniquely identify an ntp server.
Looking at the top of the ChangeLog, you might think that
Debian's 4.2.0a is
http://www.eecis.udel.edu/%7Entp/ntp_spool/ntp4/snapshots/ntp-dev/2004/05/ntp-dev-4.2.0a-20040506.tar.gz
ie the daily snapshot from 20040506 but in fact it isn't. I have
no idea what it is.
I believe this particular bug will go away when I install a kernel
with IPv6 support which I plan to do shortly.
Debian's NTP packages are clearly in a bad way !
Ian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
