"Also sprach Debian Bug Tracking System:" > I'm closing this bug as there was no response and the circumstances sound > implausible.
Response to what? This was sent out in 2005!!! Circumstances? Implausible? What? The script at that time simply refered to a routine that it hadn't defined. I have no idea if it was rectified later. But you can save the insults! I troubled to report the bug and write the missing routine. > ifup produces noise from /etc/network/if-up.d/ntpdate complaining about > the wait_for_file routine not being found (curiously, line 1 is > indicated). > > Indeed, it is used but not defined. > > A rough guess would expect it to be this routine > > + # [email protected] 18/10/08 add in missing wait_for_file() > + wait_for_file() { > + > + [ -e "$1" ] && return 0 > + local count=0 > + while sleep 1; do > + let count=count+1 > + [ -e "$1" ] && return 0 > + if [ $count -gt 60 ]; then > + return 1 > + fi > + done > + } > > > It's used lower down ... > > # This is for the case that /usr will be mounted later. > if [ -r /lib/udev/hotplug.functions ]; then > . /lib/udev/hotplug.functions > wait_for_file /usr/sbin/ntpdate-debian > ^^^^^^^^^^^^^ > fi > > -- System Information: > Debian Release: lenny/sid > APT prefers hardy-updates > APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500, > 'hardy'), (500, 'unstable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.24-19-generic (SMP w/1 CPU core) > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) > Shell: /bin/sh linked to /bin/dash > > Versions of packages ntpdate depends on: > ii libc6 2.7-15 GNU C Library: Shared libraries > ii libcap1 1:1.10-14build1 support for getting/setting > POSIX. > ii libssl0.9.8 0.9.8g-13 SSL shared libraries > ii netbase 4.34 Basic TCP/IP networking system > > Versions of packages ntpdate recommends: > ii lockfile-progs 0.1.11ubuntu1 Programs for locking and > unlocking > > ntpdate suggests no packages. > > -- no debconf information Peter -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
