From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Martin Pitt <martin.pitt@ubuntu.com>
Subject: Re: [PATCH 0/2] nfs-utils patches relating to server startup
Date: Fri, 19 Aug 2016 17:01:52 -0400 [thread overview]
Message-ID: <20160819210152.GP32329@fieldses.org> (raw)
In-Reply-To: <147157095612.26568.14161646901346011334.stgit@noble>
On Fri, Aug 19, 2016 at 11:45:56AM +1000, NeilBrown wrote:
> Two patches for recently discussed functionality.
> Both revert earlier patches and provide a more complete
> solution.
>
> The first adds a new program. I've placed this in "systemd/" rather
> than "utils/something" because that seemed to make sense. Is it
> inelegant putting code in a directory with unit files?
Seems to me like a logical enough spot in this case.--b.
>
> I don't do a lot of automake coding so if someone were to make sure I
> didn't do anything non-standard in the Makefile.am, that would be
> appreciated.
>
> Thanks,
> NeilBrown
>
> ---
>
> NeilBrown (2):
> systemd: improve ordering between nfs-server and various mounts
> mount: RPC_PROGNOTREGISTERED should not be a permanent error
>
>
> systemd/Makefile.am | 8 ++
> systemd/nfs-server-generator.c | 144 ++++++++++++++++++++++++++++++++++++++++
> systemd/nfs-server.service | 3 -
> utils/mount/stropts.c | 7 +-
> 4 files changed, 155 insertions(+), 7 deletions(-)
> create mode 100644 systemd/nfs-server-generator.c
>
> --
> Signature
next prev parent reply other threads:[~2016-08-19 21:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 1:45 [PATCH 0/2] nfs-utils patches relating to server startup NeilBrown
2016-08-19 1:45 ` [PATCH 2/2] mount: RPC_PROGNOTREGISTERED should not be a permanent error NeilBrown
2016-08-19 20:59 ` J. Bruce Fields
2016-08-19 21:37 ` NeilBrown
2016-08-20 1:25 ` J. Bruce Fields
2016-11-22 17:33 ` Steve Dickson
[not found] ` <2a0955df-2fcd-05f1-9e6f-d8a549321177@RedHat.com>
2016-11-22 22:43 ` NeilBrown
2016-11-23 18:21 ` Steve Dickson
2016-11-23 23:26 ` NeilBrown
2016-11-28 17:24 ` Steve Dickson
2016-11-29 21:36 ` NeilBrown
2016-11-29 23:05 ` Steve Dickson
2016-11-30 1:33 ` NeilBrown
2016-08-19 1:45 ` [PATCH 1/2] systemd: improve ordering between nfs-server and various mounts NeilBrown
2016-08-19 17:38 ` J. Bruce Fields
2016-08-19 20:43 ` NeilBrown
2016-08-19 21:02 ` J. Bruce Fields
2016-08-20 13:51 ` Steve Dickson
2016-08-20 15:53 ` Steve Dickson
2016-08-20 17:09 ` Steve Dickson
2016-08-19 20:37 ` [PATCH 0.5/2] Move export_d_read() to support/export/export.c NeilBrown
2016-08-19 21:01 ` J. Bruce Fields [this message]
2016-08-22 12:54 ` [PATCH 0/2] nfs-utils patches relating to server startup Steve Dickson
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=20160819210152.GP32329@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--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.