From: Paul Smith <psmith@netezza.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: How exactly does timeout work?
Date: Mon, 09 Apr 2007 13:36:35 -0400 [thread overview]
Message-ID: <1176140195.30046.225.camel@psmithub> (raw)
In-Reply-To: <x49k5wlxy4i.fsf@segfault.boston.devel.redhat.com>
On Mon, 2007-04-09 at 13:21 -0400, Jeff Moyer wrote:
> I'm not sure that the internals are really worth discussing in the man
> page
I agree with you to some extent, and I don't think the underlying method
(using an ioctl, etc.) should be documented there, but I think the
details of this algorithm can make a difference to how you decide set
the timeout value, especially for larger timeouts. It's not even really
clear (from my reading of the man page) that the timeout is "time from
the last access of the filesystem", as opposed to "how often we check to
see if anyone is using it". At the least it seems like that should be
made clear, even if the other details (how often the daemon checks for
example) are not spelled out. Maybe the text:
-t, --timeout
Set the minimum timeout, in seconds, until directories are
unmounted. The default is 5 minutes. Setting the timeout to
zero disables unmounts completely.
could be rewritten as:
-t, --timeout
Set the minimum timeout, in seconds, from the last access of the
directory until it is unmounted. The default is 5 minutes.
Setting the timeout to zero disables unmounts completely.
An extra sentence could also be added: "Access times are checked
periodically, so the actual timeout will be greater than this value.
The longer the timeout, the less frequently the access times are
checked." or something.
> We'll see what Ian thinks.
OK, cheers!
--
-----------------------------------------------------------------------------
Paul D. Smith <psmith@netezza.com> http://netezza.com
"Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
These are my opinions--Netezza takes no responsibility for them.
next prev parent reply other threads:[~2007-04-09 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 15:45 How exactly does timeout work? Paul Smith
2007-04-09 16:14 ` Jeff Moyer
2007-04-09 16:44 ` Jeff Moyer
2007-04-09 16:48 ` Paul Smith
2007-04-09 16:57 ` Jeff Moyer
2007-04-09 17:14 ` Paul Smith
2007-04-09 17:21 ` Jeff Moyer
2007-04-09 17:36 ` Paul Smith [this message]
2007-04-10 3:58 ` Ian Kent
2007-04-10 18:06 ` Jim Carter
2007-04-10 19:13 ` 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=1176140195.30046.225.camel@psmithub \
--to=psmith@netezza.com \
--cc=autofs@linux.kernel.org \
--cc=jmoyer@redhat.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.