[Pkg-sysvinit-devel] Bug#419195: initscripts: if-up.d/mountnfs should only run after all interfaces have been brought up at boot; hangs boot

[Julien BLACHE]

Package: initscripts
Version: 2.86.ds1-38
Severity: important

Hi,

I have a machine here with 2 network interfaces which mounts an NFS FS
from another machine it can only reach via its second network interface.

At boot, if-up.d/mountnfs is run after eth0 has been brought up and the boot
process hangs as it cannot mount the FS until eth1 is up.

The line in fstab looks like:
10.0.1.3:/export/foobar /mnt/foobar nfs rw,hard,intr 0 0


This is really annoying as it requires manual intervention for the machine to
boot.

JB.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages initscripts depends on:
ii  debianut 2.17                            Miscellaneous utilities specific t
ii  e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii  libc6    2.3.6.ds1-13                    GNU C Library: Shared libraries
ii  lsb-base 3.1-23.1                        Linux Standard Base 3.1 init scrip
ii  mount    2.12r-19                        Tools for mounting and manipulatin
ii  sysvinit 2.86.ds1-38                     System-V-like utilities

Versions of packages initscripts recommends:
ii  psmisc                        22.3-1     Utilities that use the proc filesy

-- no debconf information