All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Klaassen <clawsoon@yahoo.com>
To: autofs@linux.kernel.org
Subject: Indirect multi-mount map sometimes needs client reboot after update
Date: Fri, 21 May 2010 13:12:34 -0700 (PDT)	[thread overview]
Message-ID: <510030.76217.qm@web65411.mail.ac4.yahoo.com> (raw)

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.

I'm running Centos 5.2 to 5.4 with autofs-5.0.1-0.rc2.88 to autofs-5.0.1-0.rc2.143.

Thanks.

Andrew

             reply	other threads:[~2010-05-21 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 20:12 Andrew Klaassen [this message]
2010-05-24  1:36 ` Indirect multi-mount map sometimes needs client reboot after update Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=510030.76217.qm@web65411.mail.ac4.yahoo.com \
    --to=clawsoon@yahoo.com \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.