My autofs master map is in LDAP, thus I experience this issue with Jaunty 9.04 server - this is slightly different, in that NetworkManager isn't involved here.
autofs needs restarting before network mounts are available, due to incorrect starting order, as S20autofs is earlier than S35networking...thus the canonical workaround would be:
My autofs master map is in LDAP, thus I experience this issue with Jaunty 9.04 server - this is slightly different, in that NetworkManager isn't involved here.
autofs needs restarting before network mounts are available, due to incorrect starting order, as S20autofs is earlier than S35networking. ..thus the canonical workaround would be:
update-rc.d -f autofs remove
update-rc.d autofs defaults 36
however this doesn't resolve the issue, so the 'get out of jail' move is:
echo -e '#!/bin/ bash\n/ etc/init. d/autofs restart\n' >/etc/dhcp3/ dhclient- exit-hooks. d/autofs dhclient- exit-hooks. d/autofs
chmod 755 /etc/dhcp3/
This is quite a troublesome bug - this just works on Redhat 5, so gives the user a bad experience with Ubuntu 9.04 server