Your message dated Sat, 29 Jul 2006 22:04:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ntp IPv6 support fixed
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-server
Version: 1:4.2.0a-5
Severity: grave
Running ntpd by hand, or by manually extracting the init script from the
package, silently fails. No daemon is left running. Nothing is sent to the
logfile.
I would give you some debugging infirmation, but you've thoughtfully
disallowed us from helping in that way:
[/etc]# /usr/sbin/ntpd -D 4
ntpd not compiled with -DDEBUG option - no DEBUG support
usage: /usr/sbin/ntpd [ -abdgmnqx ] [ -c config_file ] [ -e e_delay ]
[ -f freq_file ] [ -k key_file ] [ -l log_file ]
[ -p pid_file ] [ -r broad_delay ] [ -s statdir ]
[ -t trust_key ] [ -v sys_var ] [ -V default_sysvar ]
[ -P fixed_process_priority ]
[/etc]#
The -n option is listed there, but is not described in the ntpd man page.
I seem to remember it meaning "don't fork off into the background," but
apparently not:
[/etc]# /usr/sbin/ntpd -n
Segmentation fault (core dumped)
[/etc]#
Sigh. Guess we won't be running a time server.
-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Kernel: Linux 2.4.22-lac13
Locale: LANG=C, LC_CTYPE=C
Versions of packages ntp-server depends on:
ii ntp 1:4.2.0a-5 Network Time Protocol: network uti
ii ntp-simple 1:4.2.0a-5 Network Time Protocol: daemon for
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:4.2.2+dfsg-1
Crashes caused by lack of IPv6 support in some part of the system have
been addressed in 4.2.2, which should take care of this bug.
--- End Message ---
