Bug#496007: initscripts: if-up.d/mountnfs should not try to wait for all auto interfaces
Vincent Lefevre
vincent at vinc17.net
Fri Feb 21 14:03:18 GMT 2025
On 2025-02-21 14:25:31 +0100, Vincent Lefevre wrote:
> Fri Aug 22 02:38:44 2008: Configuring network interfaces...eth0: error fetching interface information: Device not found
> Fri Aug 22 02:38:47 2008: Ignoring unknown interface eth0=eth0.
> Fri Aug 22 02:38:48 2008: if-up.d/mountnfs[eth1]: waiting for interface eth0 before doing NFS mounts (warning).
> ^^^^ ^^^^
>
> The mismatch between the interface names is unexpected.
> If it was really waiting for interface eth1, this is OK.
> If it was waiting for interface eth0 (hardcoded?), then
> this is wrong.
>
> In any case, the log message looks wrong.
I now see that this was expected:
exit_unless_last_interface() {
ifaces="$(ifquery --list)"
for i in $ifaces ; do
if [ "$i" = "lo" ]; then
continue
fi
if ! ifquery --state $i >/dev/null ; then
msg="if-up.d/mountnfs[$IFACE]: waiting for interface $i before doing NFS mounts"
log_warning_msg "$msg"
exit 0
fi
done
}
# Wait until all auto interfaces are up before attempting to mount
# network file systems.
exit_unless_last_interface
I thought that this caused a slowdown of the boot, as there were
a delay of several seconds after this log message. But it was
probably unrelated.
I do not use sysvinit any longer (on any machine). But note that the
above logic might be wrong since "auto" is not the only way to bring
interfaces up. Later, I used netplugd (from the netplug package).
There was also allow-hotplug (which was not existing yet when I had
initially installed the machine).
--
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
More information about the Debian-init-diversity
mailing list