From: Michael Blandford <mlblandf@sedona.ch.intel.com>
To: Bryan O'Sullivan <bos@serpentine.com>
Cc: autofs@linux.kernel.org
Subject: Re: Severe problem with 4.1.2: automount caches NIS maps forever
Date: Thu, 06 May 2004 14:22:38 -0700 [thread overview]
Message-ID: <409AAC9E.9000505@sedona.intel.com> (raw)
In-Reply-To: <1083865163.18740.6.camel@serpentine.internal.keyresearch.com>
Bryan O'Sullivan wrote:
>Hi -
>
>The autofs 4.1.2 release has a change in behaviour from earlier releases
>(4.1.0, I think, and 4.0.0 for sure) in that it never checks to see if a
>NIS-based automount map has changed. This means that if I change the
>location of an autofs-mounted filesystem, I have to SIGHUP the automount
>daemons on every machine that care about that filesystem so that they'll
>forget the contents of the map and reload it.
>
>Needless to say, this doesn't scale in even a tiny way :-(
>
>
Agreed. You would think with all the testing I have done, I would have
seen this one.
I can easily replicate it and fix it with a SIGHUP.
Ian, do you have any thoughts on this one?
Michael
Disclaimer: The content of this message is my personal opinion only and
although I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak on
behalf of Intel on this matter.
next prev parent reply other threads:[~2004-05-06 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 17:39 Severe problem with 4.1.2: automount caches NIS maps forever Bryan O'Sullivan
2004-05-06 18:11 ` mmarion
2004-05-06 21:07 ` Tom Georgoulias
2004-05-06 21:22 ` Michael Blandford [this message]
2004-05-07 2:10 ` Ian Kent
2004-05-07 3:45 ` Jim Carter
2004-05-07 4:23 ` Ian Kent
2004-05-07 18:45 ` Michael Blandford
2004-05-08 5:20 ` raven
2004-05-09 6:11 ` Jim Carter
2004-05-07 17:58 ` Bryan O'Sullivan
2004-05-08 5:44 ` raven
2004-05-08 21:26 ` Bryan O'Sullivan
2004-05-09 3:59 ` raven
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=409AAC9E.9000505@sedona.intel.com \
--to=mlblandf@sedona.ch.intel.com \
--cc=autofs@linux.kernel.org \
--cc=bos@serpentine.com \
/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.