From: "Rüdiger Meier" <sweet_f_a@gmx.de>
To: linux-nfs@vger.kernel.org
Cc: Tom Gundersen <teg@jklm.no>, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [RFC][PATCH] libtirpc,rpcbind: move socket from /var/run to /run
Date: Fri, 9 Dec 2011 00:40:33 +0100 [thread overview]
Message-ID: <201112090040.35286.sweet_f_a@gmx.de> (raw)
In-Reply-To: <1323371940-9140-1-git-send-email-teg@jklm.no>
On Thursday 08 December 2011, Tom Gundersen wrote:
> /run is guaranteed to be available and writeable at any time, whereas
> /var might be on a separate partition and hence not available during
> early boot. By moving the socket from /var to /run we are able to use
> rpcbind earlier, which would in particular make a difference in case
> /var is on an nfs mount, something I am currently seeing bug reports
> about.
I don't have /run on any system so IMHO it's not really guaranteed. Does
it will be created if not existent? I hope not.
cu,
Rudi
prev parent reply other threads:[~2011-12-08 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 19:19 [RFC][PATCH] libtirpc,rpcbind: move socket from /var/run to /run Tom Gundersen
2011-12-08 21:40 ` Chuck Lever
2011-12-08 23:05 ` Tom Gundersen
2011-12-08 23:11 ` Chuck Lever
2011-12-08 23:40 ` Rüdiger Meier [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=201112090040.35286.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-nfs@vger.kernel.org \
--cc=teg@jklm.no \
/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).