From: Ian Kent <raven@themaw.net>
To: Stef Bon <stef@bononline.nl>
Cc: autofs@linux.kernel.org
Subject: Re: How to determine a path is a mountpoint.
Date: Tue, 23 Feb 2010 00:38:55 +0800 [thread overview]
Message-ID: <4B82B31F.5060400@themaw.net> (raw)
In-Reply-To: <201002221730.28243.stef@bononline.nl>
On 02/23/2010 12:30 AM, Stef Bon wrote:
> On Monday 22 February 2010 04:54:03 Ian Kent wrote:
>
>
>>>
>>> So, am I missing here something? Or has something changed?
>>> When I look to the various init rc scripts, the file
>>> /etc/sysconfig/autofs file is sourced.
>>
>> In the init script the sourcing of the configuration is redundant but
>> environment variables that are exported will be seen by child processes
>> (as per normal shell environment variable export rules) and can be used
>> to over-ride the settings in the autofs configuration. Note that the
>> internal autofs default is BROWSE_MODE="yes" and that is set to "no" by
>> the default installed configuration for backward compatibility.
>
>
> Now when I export them all, they are detected and used. I see logging and browse mode is set to no.
>
> OK now I'm beginning to understand, the automounter reads the configuration values directly, from the default configuration file.
> I thought the automounter reads them from the environement, cause the conf file is sourced at the beginning of the init file.
>
> I've found the code. This is, and it happens to me more often, not well documented. Please start a wiki or something.
> I know you are very busy, I recieved some copies of emails about an important issue this weekend.
>
> I'm working also a lot with FUSE, and the wiki there provides a lot of information, although it's not complete.
> I would like to help if I can.
Yeah, a wiki would be useful but unless we can get a group of us (at
least three people) interested in working on it (and get access details
sorted out) I'm reluctant to set the request for a kernel.org autofs
wiki in motion.
I must admit I'm not keen on having to maintain a wiki site, as I've
said before, purely because in my experience, it's actually quite a bit
of work to make and keep it useful.
>
> Stef Bon
>
>>
>> The USE_MISC_DEVICE is the only exception. It is used only by the init
>> script for checking if /dev/autofs is present and if we want to use
>> /dev/autofs for kernel communication.
>>
>> Ian
prev parent reply other threads:[~2010-02-22 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 21:53 How to determine a path is a mountpoint Stef Bon
2010-02-16 3:04 ` Ian Kent
2010-02-16 13:20 ` Stef Bon
2010-02-16 17:29 ` Ian Kent
2010-02-17 12:43 ` Stef Bon
2010-02-17 14:25 ` Ian Kent
2010-02-18 23:18 ` Stef Bon
2010-02-19 3:57 ` Ian Kent
2010-02-19 14:11 ` Stef Bon
[not found] ` <201002211428.39077.stef@bononline.nl>
2010-02-22 3:54 ` Ian Kent
2010-02-22 16:30 ` Stef Bon
2010-02-22 16:38 ` Ian Kent [this message]
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=4B82B31F.5060400@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=stef@bononline.nl \
/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.