Hello to all reporters of this issue. It seems to me that the upstream
encoded requirements for autofs:
# Required-Start: $network $ypbind
# Required-Stop: $network $ypbind
Have not been properly captured in the upstart job:
start on (filesystem
and net-device-up IFACE!=lo)
stop on runlevel [!2345]
$ypbind is particularly tricky because it has not been converted to
upstart yet. That is bug #569757
That said, until that bug is fixed, we can just start ypbind in the pre-
start, alleviating this problem.
For $network, the exact meaning of this has never been clear[1], so
emitting it when "the first real interface" is up is probably a decent
best effort.
Given all of that, and the fact that we are the upstream for the upstart
job, I am marking this as Triaged.
1. http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-
Core-generic/facilname.html
** Changed in: autofs (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in ubuntu.
https://bugs.launchpad.net/bugs/573919
Title:
autofs doesn't work with lucid
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
