From: Ian Kent <raven@themaw.net>
To: "Breitman, Jason" <Jason.Breitman@blackrock.com>
Cc: "'autofs@linux.kernel.org'" <autofs@linux.kernel.org>
Subject: Re: autofs miscellaneous device
Date: Fri, 24 Sep 2010 22:17:21 +0800 [thread overview]
Message-ID: <1285337841.2967.40.camel@localhost> (raw)
In-Reply-To: <4A961A51CBE84C429C56E5734477BD1F2CBAAA1AA0@EXCHAMRS03.na.blkint.com>
On Thu, 2010-09-23 at 11:36 -0400, Breitman, Jason wrote:
> USE_MISC_DEVICE=boolean
> A boolean to enable (yes) or disable (no) using the autofs miscellaneous device. For example:
>
> Can someone explain to me what this option does?
> What are the pros and cons of having USE_MISC_DEVICE=yes?
> I am not able to find details online.
It provides access to the new ioctl interface.
There is a description of what it does, why it has been done and how it
can be used in the kernel source tree:
Documentation/filesystems/autofs4-mount-control.txt
Probably the biggest impact of using this, if it is available, is that
autofs can check if a path is a mount without scanning and file based
table. Clearly, if you don't have a lot of mounts it may not give any
real improvement.
It is also needed to allow automount to "re-connect" to mounts that were
busy and left mounted during a restart. Previously processes using these
mounts would forget their working directory because of the lazy umount
that was done to clear them at startup.
>
>
> Jason Breitman
> jason.breitman@blackrock.com
>
> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED. If this message was misdirected, BlackRock, Inc. and its subsidiaries, ("BlackRock") does not waive any confidentiality or privilege. If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of BlackRock, unless the author is authorized by BlackRock to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic storage and r
eview by BlackRock. Although BlackRock operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
prev parent reply other threads:[~2010-09-24 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:36 autofs miscellaneous device Breitman, Jason
2010-09-24 14:17 ` 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=1285337841.2967.40.camel@localhost \
--to=raven@themaw.net \
--cc=Jason.Breitman@blackrock.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.