Update for whoever gets here:
I triet with "bobootwait" but it failed like I anticipated it.
After some digging and source-reading I found out the following: mountall tries
to mount the network volume and if it does not work, it will wait for the
device by waiting for a SIGUSR. upstart sends SI
Hi Mr. Remnant
Setting fstab to "nobootwait" is not a solution. /home has to be there before
any user gets a login
If there is no home directory for the user and gdm and login will fail.
And my users complain heavily and start to press the reset button or c-a-del
every time they get "waiting for
Public bug reported:
Binary package hint: mountall
I mount my /home directory from an nfs4 server by using an entry in fstab:
svr.x.de:/ /home nfs4rw,sec=krb5 0 0
at reboot i get follogwing error
mount.nfs4: no such device
mountall: mount /home [...] terminated with status