From: rnews@tasking.nl
To: nfs@lists.sourceforge.net
Subject: Re: inconsistencies in nfs(5)
Date: Thu, 09 Aug 2007 16:04:40 -0000 [thread overview]
Message-ID: <169a.46bb3b18.7157f@altium.nl> (raw)
In-Reply-To: 46BB2DF2.1050501@oracle.com
Chuck Lever <chuck.lever@oracle.com> wrote:
| + The description for the "bg" option claims "After a mount operation
| is backgrounded, all subsequent mounts on the same NFS server will be
| backgrounded immediately, without first attempting the mount." I don't
| think there's logic to do that in either the legacy mount command or in
| mount.nfs. Should this text be removed from the man page?
I added that text in 1997, in a patch that was included in mount-2.7g.
It referred to the following fragment in nfsmount.c:
+ /*
+ * If the previous mount operation on the same host was
+ * backgrounded, and the "bg" for this mount is also set,
+ * give up immediately, to avoid the initial timeout.
+ */
+ if (bg && !running_bg &&
+ prev_bg_host && strcmp(hostname, prev_bg_host) == 0) {
+ if (retry > 0)
+ retval = EX_BG;
+ return retval;
+ }
This code got removed somewhere after util-linux-2.12p, but I don't
know the details.
--
Dick Streefland //// Altium BV
dick.streefland@altium.nl (@ @) http://www.altium.com
--------------------------------oOO--(_)--OOo---------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-09 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 15:08 inconsistencies in nfs(5) Chuck Lever
2007-08-09 16:04 ` rnews [this message]
2007-08-09 16:27 ` Chuck Lever
2007-08-10 8:18 ` rnews
2007-08-13 14:18 ` Chuck Lever
2007-08-15 20:34 ` Chuck Lever
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=169a.46bb3b18.7157f@altium.nl \
--to=rnews@tasking.nl \
--cc=dick.streefland@altium.nl \
--cc=nfs@lists.sourceforge.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.