The fix for this:
--- autofs5-5.0.5/debian/autofs5.autofs.upstart +++ autofs5-5.0.5/debian/autofs5.autofs.upstart @@ -4,56 +4,15 @@ start on (filesystem - and net-device-up IFACE!=lo) + and net-device-up + and mounting TYPE=nfs) stop on runlevel [!2345]
Causes mountall to fail to mount any NFS mounts in /etc/fstab.
The reason is mounting TYPE=nfs comes every time an NFS mount is *attempted* ... even when it will fail..
TO test this:
Add this to /etc/fstab (replacing ip/dir with a valid NFS mount of course):
192.168.122.1:/home/clint /mnt nfs ro,nolock 0 0
With the previous version of autofs, this would work fine on reboot. Now install 5.0.5-0ubuntu5 .. on reboot, /mnt will not be mounted.
Also there is no explanation given as to why we are now ignoring /etc/default/autofs which is a bug since upgrades from Maverick will break.
The fix for this:
--- autofs5- 5.0.5/debian/ autofs5. autofs. upstart 5.0.5/debian/ autofs5. autofs. upstart
+++ autofs5-
@@ -4,56 +4,15 @@
start on (filesystem
- and net-device-up IFACE!=lo)
+ and net-device-up
+ and mounting TYPE=nfs)
stop on runlevel [!2345]
Causes mountall to fail to mount any NFS mounts in /etc/fstab.
The reason is mounting TYPE=nfs comes every time an NFS mount is *attempted* ... even when it will fail..
TO test this:
Add this to /etc/fstab (replacing ip/dir with a valid NFS mount of course):
192.168. 122.1:/ home/clint /mnt nfs ro,nolock 0 0
With the previous version of autofs, this would work fine on reboot. Now install 5.0.5-0ubuntu5 .. on reboot, /mnt will not be mounted.
Also there is no explanation given as to why we are now ignoring /etc/default/autofs which is a bug since upgrades from Maverick will break.