Bug#345549: nfs: Mounting in background hangs boot process until doing ctrl+c if server is unvailaible

[MaX]

Martin Michlmayr wrote: * KnuX <[EMAIL PROTECTED]> [2006-01-01 18:45]: I have two PC under Debian Unstable : A server (PC-Server) and a client (PC-Client). What does dpkg -l | grep nfs say on your server? PC-Server : $ dpkg -l | grep nfs ii  libnfsidmap1                  0.8-1                          An nfs idmapping library ii  nfs-common                    1.0.7-3                        NFS support files common to client and server ii  nfs-kernel-server             1.0.7-3                        Kernel NFS server support $ dpkg -l | grep mount ii  mount                         2.12r-2                        Tools for mounting and manipulating filesystems ii  pmount                        0.8-2                          mount removable devices as normal user PC-Client : $ dpkg -l | grep nfs ii  libnfsidmap1                     0.8-1                         An nfs idmapping library ii  nfs-common                       1.0.7-3                       NFS support files common to client and server ii  nfs-kernel-server                1.0.7-3                       Kernel NFS server support $ dpkg -l | grep mount ii  mount                            2.12r-2                       Tools for mounting and manipulating filesystems ii  pmount                           0.8-2                         mount removable devices as normal user ii  smbfs                            3.0.21a-1                     mount and umount commands for the smbfs (for kernels >= th I reproduce this problem on a Debian testing : http://194.146.225.66/~max/nfs.png As you can see, the latest line is a punct ".". Actually, I have the "done." message and nothing else. The only way I found to resume the boot process is to type "CTRL+C", and no background mount is done... So I have to mount manually the NFS shares. I'm not a developper, but I think that the mount start-up script doesn't return. Are you sure it *never* returns? Maybe there's just some kind of time-out you haven't yet reached. Have you tried waiting for a few minutes? One day, due to a power failure, it stays on the "." message during 3 hours. So there is no timeout ;) KnuX