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=''
Ok, I've investigated this, and it turn out:
statd-mounting.conf intercepts nfs mounts and waits for the statd daemon to be run filesystems and started portmap ON_BOOT=y)
statd.conf starts on (virtual-
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=''