Ok, I've investigated this, and it turns out:
statd-mounting.conf intercepts nfs mounts and waits for the statd daemon to be
run
statd.conf starts on (virtual-filesystems and started portmap ON_BOOT=y)
rpcbind.conf is what emits the started portmap event:
# For compatibility with older upstart jobs in Ubuntu
post-start exec initctl emit --no-wait started JOB=portmap ON_BOOT=$ON_BOOT
pre-stop exec initctl emit --no-wait stopping JOB=portmap
But, to actually work with upstart in 14.10, the INSTANCE variable has to be
added, like so:
# For compatibility with older upstart jobs in Ubuntu
post-start exec initctl emit --no-wait started JOB=portmap INSTANCE=''
ON_BOOT=$ON_BOOT
pre-stop exec initctl emit --no-wait stopping JOB=portmap INSTANCE=''
** This bug is no longer a duplicate of bug 1384502
fstab entry for nfs /home fails to mount on boot
** Package changed: mountall (Ubuntu) => upstart (Ubuntu)
** Also affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nfs-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391296
Title:
14.10: NFS drives in fstab not mounted automatically
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
