From: "H. Peter Anvin" <hpa@zytor.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: making the mountpoints visible all the time (fwd)
Date: Fri, 21 Nov 2003 11:56:31 -0800 [thread overview]
Message-ID: <3FBE6DEF.5020202@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0311211453250.6131-100000@wombat.indigo.net.au>
Ian Kent wrote:
>
> The above works that way without the update.
>
> I'm not sure that a periodic update really gets us much. Since in most
> sites maps change infrequently.
>
> On the other hand at work we run a cron every night on all our machines to
> trigger an update of the maps.
>
> So I'm on the fence here?
>
Oh yes, a lot of map types support querying "has a change occurred"
(usually in the form of a generation number, or in the case of a file
map, the mtime.) This absolutely should be taken advantage of.
(For a program map, this complicates the protocol somewhat. I don't
know necessarily of the best way to deal with that. It needs some
thinking :)
-hpa
next prev parent reply other threads:[~2003-11-21 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 8:13 making the mountpoints visible all the time (fwd) Ian Kent
2003-11-19 16:45 ` H. Peter Anvin
2003-11-21 0:51 ` Ian Kent
2003-11-21 1:43 ` H. Peter Anvin
2003-11-21 6:59 ` Ian Kent
2003-11-21 8:49 ` Ruslan U. Zakirov
2003-11-22 7:14 ` Ian Kent
2003-11-21 19:52 ` H. Peter Anvin
2003-11-21 19:56 ` H. Peter Anvin [this message]
2003-11-22 7:19 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 5:05 Chris Croswhite
2003-11-17 5:32 ` Ian Kent
2003-12-02 13:49 ` Ian Kent
2003-11-16 16:05 Ian Kent
2003-11-16 19:58 ` Alexander Macdonald
2003-11-17 2:53 ` 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=3FBE6DEF.5020202@zytor.com \
--to=hpa@zytor.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/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.