From: Tom Georgoulias <tom.georgoulias@freescale.com>
To: raven@themaw.net
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: mount point created if automount map is empty during daemon startup?
Date: Tue, 04 May 2004 10:43:29 -0500 [thread overview]
Message-ID: <4097BA21.5060307@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0405042334080.17014@donald.themaw.net>
raven@themaw.net wrote:
> We'll leave this to the people on the list to decide whether this
> behaviour should be changed.
Well, from our point of view, it is nice to be able to create maps that
are empty at first and not have to worry about populating them until
later. This gives us our group the flexibility to plan out in advance
how our mounts will look, put the necessary mount points in place during
the regular maintenance intervals (by rebooting the systems, something
we can't always do), and adding map entries later on as the data is
moved to the new location.
Just my two cents.
Tom
--
Tom Georgoulias
POPI Classification
[x] General Business Information
[] Freescale Semiconductor Internal Use
[] Freescale Semiconductor Confidential Proprietary
next prev parent reply other threads:[~2004-05-04 15:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 12:58 An offer to host autofs.org raven
2004-05-03 17:55 ` Tim Hockin
2004-05-04 0:32 ` Axel Thimm
2004-05-04 1:10 ` Ian Kent
2004-05-04 1:09 ` Tim Hockin
2004-05-04 1:21 ` humm " Alvin Oga
2004-05-04 12:25 ` Axel Thimm
2004-05-04 14:37 ` mount point created if automount map is empty during daemon startup? Tom Georgoulias
2004-05-04 14:53 ` raven
2004-05-04 15:26 ` Tom Georgoulias
2004-05-04 15:37 ` raven
2004-05-04 15:43 ` Tom Georgoulias [this message]
2004-05-04 15:52 ` raven
2004-05-04 15:27 ` raven
2004-05-04 15:05 ` Jeff Moyer
2004-05-04 15:22 ` raven
2004-05-04 15:37 ` Tom Georgoulias
2004-05-04 15:57 ` raven
2004-05-04 20:41 ` Tom Georgoulias
2004-05-05 1:08 ` Ian Kent
2004-05-04 18:04 ` An offer to host autofs.org H. Peter Anvin
2004-05-04 18:21 ` fork - " Alvin Oga
2004-05-04 18:26 ` Michael Blandford
2004-05-04 21:16 ` Mike Waychison
2004-05-04 21:50 ` Axel Thimm
2004-05-04 22:04 ` Mike Waychison
2004-05-05 1:16 ` 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=4097BA21.5060307@freescale.com \
--to=tom.georgoulias@freescale.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.