From: Mike Frysinger <vapier@gentoo.org>
To: NeilBrown <neilb@suse.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
libtirpc-devel@lists.sourceforge.net
Subject: Re: [Libtirpc-devel] [PATCH rpcbind] Move default state-dir to /run/rpcbind
Date: Fri, 11 Nov 2016 13:00:34 -0800 [thread overview]
Message-ID: <20161111210034.GM21655@vapier.lan> (raw)
In-Reply-To: <877f8almcf.fsf@notabene.neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On 11 Nov 2016 14:36, NeilBrown wrote:
> rpcbind can save state in a file to allow restart without forgetting
> about running services.
>
> The default location is currently "/tmp" which is an over-used
> directory that isn't really suitable for system files.
> The modern preferences would be a subdirectory of "/run", which can
> be selected with a ./configure option. That subdirectory would still need
> to be created by something.
the portable path is /var/cache instead of /run. i don't think libtirpc
should be configuring itself to assume Linux by default.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-11 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 3:36 [PATCH rpcbind] Move default state-dir to /run/rpcbind NeilBrown
2016-11-11 21:00 ` Mike Frysinger [this message]
2016-11-13 23:09 ` [Libtirpc-devel] " NeilBrown
2016-11-14 7:05 ` [PATCH rpcbind v2] Move default state-dir to a subdirectory of /tmp NeilBrown
2016-11-15 19:54 ` [Libtirpc-devel] " Steve Dickson
2016-11-16 1:34 ` NeilBrown
2016-11-16 10:17 ` Steve Dickson
2016-11-14 19:12 ` [Libtirpc-devel] [PATCH rpcbind] Move default state-dir to /run/rpcbind Mike Frysinger
2016-11-14 19:26 ` Steve Dickson
2016-11-14 20:12 ` Mike Frysinger
[not found] ` <669e90b0-6011-7b82-4e37-f1e3bf292026@RedHat.com>
2016-11-15 6:36 ` NeilBrown
2016-11-15 16:02 ` Steve Dickson
2016-11-15 20:28 ` 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=20161111210034.GM21655@vapier.lan \
--to=vapier@gentoo.org \
--cc=SteveD@redhat.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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.