Actually, I'm going to reopen this bug against portmap. :) The portmap
upstart conversion introduced a dependency on the loopback interface
that wasn't there before; previously portmap would start fine as long as
/any/ network interface was up. And I think some systems, such as
vserver, explicitly don't have lo available as an interface within the
container. So even though it doesn't seem sensible to have a system
without localhost, we want portmap to be as robust as possible here.
** Package changed: nfs-utils (Ubuntu) => portmap (Ubuntu)
** Changed in: portmap (Ubuntu)
Importance: Undecided => Low
** Changed in: portmap (Ubuntu)
Status: Invalid => Triaged
--
nfs-kernel-server doesn't start automatically at startup
https://bugs.launchpad.net/bugs/455045
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
