[Bug 119660] Re: Autofs should be reloaded when state of network interface changes

[Neil Broadley]

Since this still appears to be an issue on Trusty (14.04) and the Debian
bugtracker notes that they're no longer tracking autofs in unstable,
what happens to this bug?

And is it still the case that autofs (now version 5 in Trusty's repo's)
doesn't use upstart? I'm going to try the solution presented in the bug
description, but is that workaround still the most appropriate fix for
what seems to be a pretty glaring ommision in autofs functionality?

How do corporates join their laptops to their network shares over WIFI
reliably when autofs is effectively broken in this case?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/119660

Title:
  Autofs should be reloaded when state of network interface changes

Status in “autofs” package in Ubuntu:
  Triaged
Status in “autofs” package in Debian:
  Fix Released

Bug description:
  Binary package hint: autofs

  At the moment the autofs deamon is started by a regular init script. If the autofs daemon loads its configuration from the network (NIS or LDAP), the configuration is only available after the network interface is up.
  Using the init script, the autofs daemon tries to load the configuration when the network interface is not yet ready (e.g. no DHCP address assigned yet, etc). 
  I suggest to put a little script in /etc/network/if-up.d/ and /etc/network/if-down.d/ to reload the autofs daemon, so that the configuration gets updated when the state of one of the network interfaces changes.

  At the moment I'm using a very simple script on my machine:
  #!/bin/sh
  # Not for loopback!
  [ "$IFACE" != "lo" ] || exit 0
  /etc/init.d/autofs reload

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/119660/+subscriptions