Re: Indirect multi-mount map sometimes needs client reboot after update

[Ian Kent <raven@themaw.net>]

On Fri, 2010-05-21 at 13:12 -0700, Andrew Klaassen wrote:
> I've got indirect multi-mount and single-mount maps set up in NIS like
> so:
> 
> auto.master:
> 
> /test auto.test --ghost
> 
> auto.test:
> 
> foo /    -tcp,intr server1:/foo \
>     /bar -tcp,intr server2:/bar
> abc      -tcp,intr server1:/abc
> 
> Changes to single-mount maps are picked up immediately by clients.
> 
> Changes to multi-mount maps are picked up:
> 
> 1. Immediately if nothing under the key is currently mounted.
> 
> 2. Only after an autofs restart - or sometimes even a reboot - after
> anything has been mounted under the key.
> 
> Is it possible to make #2 go away?  Having to reboot every single one
> of hundreds of client machines after a single change is a downer.

These multi-mount map entry keys should be updated, if they have
changed, after all the dependent mounts in the tree have been umounted.
They can't be updated while subordinate mounts are active because the
information about the mount tree (and dependencies within the tree) is
used during operation.

Are you sure the mount tree goes away and isn't updated at the next
mount?

Ian