Package: ntpdate Version: 1:4.2.0a-8 Severity: normal Followup-For: Bug #289267
This seems to be the most sensible thing to do. I have a PCMCIA wireless interface which is not started before ntpdate starts in S runlevel. Sometimes this is the only connection to the outside, sometimes the machine's builtin ethernet is connected, in which case ntpdate should run during S so that the time is set as soon as possible. So run ntpdate during S if a net connection is present, but also run it in ifup scripts so that a hotplug net connection will cause it to be invoked as well. You could make this optional in the default file - maybe not everyone wants ntpdate to run every time an interface is plugged. Also probably check for ntpd (or any program on ntpd port) running and abort if it is so that we don't confuse it. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.25 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages ntpdate depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an -- debconf information: * shared/ntp/servers: time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
