[Bug 711425] Re: portmap does not stop during shutdown, causing possible root fs corruption

[Brian Murray]

** Changed in: portmap (Ubuntu Maverick)
   Importance: Undecided => High

** Changed in: portmap (Ubuntu Maverick)
       Status: New => Triaged

** Changed in: sysvinit (Ubuntu Lucid)
   Importance: Undecided => High

** Changed in: sysvinit (Ubuntu Lucid)
       Status: New => Triaged

** Changed in: sysvinit (Ubuntu Maverick)
   Importance: Undecided => High

** Changed in: sysvinit (Ubuntu Maverick)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/711425

Title:
  portmap does not stop during shutdown, causing possible root fs
  corruption

Status in “portmap” package in Ubuntu:
  In Progress
Status in “sysvinit” package in Ubuntu:
  In Progress
Status in “portmap” source package in Lucid:
  Triaged
Status in “sysvinit” source package in Lucid:
  Triaged
Status in “portmap” source package in Maverick:
  Triaged
Status in “sysvinit” source package in Maverick:
  Triaged

Bug description:
  Binary package hint: portmap

  This is related, but not the same, as bug #672177

  portmap should be stopped as soon as it is no longer needed, which is
  right after NFS filesystems are unmounted. The unmounting is done by
  unmountnfs.sh from sysvinit. It properly defines an LSB header to say
  that portmap should be stopped after it. The trouble is that nothing
  interprets this header anymore as upstart does not support this method
  of shutdown.

  When libc6 is upgraded, this means portmap keeps /lib/libc.so.xxxxx
  open, and so / cannot be remounted as readonly, causing filesystem
  corruption (this was reported in the comments of bug #672177 by
  "ingo".

  So portmap should define an event to stop on and sysvinit should emit
  that event when it happens.