[Bug 776407] Re: init: portmap-wait (statd) main process (693) killed by TERM signal

[Steve Langasek]

> Since it also uses a script, this means as soon as the script
> has started running the started event is likely emitted,

This should not be the case.  The script is:

        if [ -f "$DEFAULTFILE" ]; then
            . "$DEFAULTFILE"
        fi

        if [ "x$NEED_STATD" != xno ]; then
                exec rpc.statd -L $STATDOPTS
        fi

These are all shell builtins (by design) until rpc.statd execs.  So the
first fork is within rpc.statd.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/776407

Title:
  init: portmap-wait (statd) main process (693) killed by TERM signal

Status in “nfs-utils” package in Ubuntu:
  New

Bug description:
  the client log says:
  Apr  4 12:23:29 server init: portmap-wait (statd) main process (693) killed by TERM signal
  Apr  4 12:23:29 server init: statd-mounting main process (679) killed by TERM signal
  Apr  4 12:23:29 server rpc.statd[947]: Version 1.1.6 Starting
  Apr  4 12:23:29 server rpc.statd[947]: Flags: 

  Although the mount points are defined in /etc/fstab, they don't mount
  upn boot. I have to mount them manually

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/776407/+subscriptions