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 13:25:31 GMT 2025


Hi Mark,

On 2025-02-19 14:54:21 +0000, Mark Hindley wrote:
> I am unclear what you are really wanting here. How is
> if-up.d/mountnfs supposed to determine which auto interfaces are
> important and which it can ignore?

This is what I had in the logs:

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.

Note also that AFAIK, interface names have been stabilized since 2008.
So errors like "error fetching interface information: Device not found"
should no longer occur.

-- 
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