From: NeilBrown <neilb@suse.com>
To: Steve Dickson <SteveD@RedHat.com>
Cc: systemd-devel@freedesktop.org, linux-nfs@vger.kernel.org
Cc: Lennart Poettering <lennart@poettering.net>
Subject: [PATCH] nfs.man: document incompatibility between "bg" option and systemd.
Date: Tue, 30 May 2017 08:19:16 +1000 [thread overview]
Message-ID: <87tw43fgrf.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20170529133814.GC17967@gardel-login>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
Systemd does not, and will not, support "bg" correctly.
It has other, better, ways to handle "background" mounting.
Explain this.
See also https://github.com/systemd/systemd/issues/6046
Signed-off-by: NeilBrown <neilb@suse.com>
---
utils/mount/nfs.man | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index cc6e992ed807..7e76492d454f 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -372,6 +372,21 @@ Alternatively these issues can be addressed
using an automounter (refer to
.BR automount (8)
for details).
+.IP
+When
+.B systemd
+is used to mount the filesystems listed in
+.IR /etc/fstab ,
+the
+.B bg
+option is not supported, and may be stripped from the option list.
+Similar functionality can be achieved by providing the
+.B x-system.automount
+option. This will cause
+.B systemd
+to attempt to mount the filesystem when the mountpoint is first
+accessed, rather than during system boot. The mount still happens in
+the "background", though in a different way.
.TP 1.5i
.BR rdirplus " / " nordirplus
Selects whether to use NFS v3 or v4 READDIRPLUS requests.
@@ -1810,7 +1825,8 @@ such as security negotiation, server referrals, and named attributes.
.BR rpc.idmapd (8),
.BR rpc.gssd (8),
.BR rpc.svcgssd (8),
-.BR kerberos (1)
+.BR kerberos (1),
+.BR systemd.mount (5) .
.sp
RFC 768 for the UDP specification.
.br
--
2.12.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-29 22:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 2:46 systemd and NFS "bg" mounts NeilBrown
2017-05-29 13:38 ` [systemd-devel] " Lennart Poettering
2017-05-29 22:05 ` NeilBrown
2017-05-29 22:19 ` NeilBrown [this message]
2017-05-30 4:47 ` [PATCH] nfs.man: document incompatibility between "bg" option and systemd Niels de Vos
2017-05-30 7:40 ` [systemd-devel] " Michael Biebl
2017-05-30 8:55 ` NeilBrown
2017-05-30 9:15 ` Michael Biebl
2017-05-30 12:45 ` Lennart Poettering
2017-05-30 12:43 ` Lennart Poettering
2017-06-06 18:07 ` Steve Dickson
2017-06-06 19:57 ` [systemd-devel] " Michael Biebl
2017-06-07 8:13 ` Lennart Poettering
2017-06-07 9:42 ` Steve Dickson
2017-06-06 21:49 ` NeilBrown
2017-06-07 10:08 ` Steve Dickson
2017-06-07 12:02 ` Lennart Poettering
2017-06-07 19:48 ` Steve Dickson
2017-06-08 5:16 ` NeilBrown
2017-06-08 15:36 ` J. Bruce Fields
2017-06-08 21:54 ` NeilBrown
2017-06-08 20:24 ` Steve Dickson
2017-06-07 8:12 ` Lennart Poettering
2017-06-07 10:04 ` Steve Dickson
2017-06-07 16:08 ` J. Bruce Fields
2017-06-08 20:34 ` Steve Dickson
2017-07-04 22:20 ` NeilBrown
2017-07-10 15:26 ` Steve Dickson
2017-07-10 22:56 ` NeilBrown
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=87tw43fgrf.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=SteveD@RedHat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=systemd-devel@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).