[Bug 569094] Re: Upstart gssd.conf: stopping prematurely with kerberized NFS4 mounts

Steve Langasek steve.langasek at canonical.com
Wed Oct 10 16:17:48 UTC 2012


This was fixed in quantal with nfs-utils 1:1.2.6-3ubuntu2:

   * Fix the stop conditions: never stop on 'runlevel [06]' since that gives
     the system no time to cleanly unmount nfs mounts; instead, stop only on
     the unmounted-remote-filesystems event.  LP: #569094.


** Changed in: nfs-utils (Ubuntu)
       Status: Triaged => Fix Released

-- 
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/569094

Title:
  Upstart gssd.conf: stopping prematurely with kerberized NFS4 mounts

Status in “nfs-utils” package in Ubuntu:
  Fix Released
Status in “nfs-utils” source package in Lucid:
  Won't Fix

Bug description:
  /etc/init/gssd.conf states:
    stop on (stopping portmap or runlevel [06])

  When going to runlevel 0 or 6, this results in unusable (and even
  hanging) Kerberized NFS4 mounts - i.e. if there's any process still
  using anything on nfs4, it can't continue because gssd isn't there
  anymore.

  The right moment to stop gssd would probably be after unmounting any
  NFS4 mounts.

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




More information about the foundations-bugs mailing list