From: Steve Dickson <SteveD@RedHat.com>
To: NeilBrown <neilb@suse.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [nfs-utils PATCH] Add RemainAfterExit to two services.
Date: Thu, 12 Oct 2017 10:20:46 -0400 [thread overview]
Message-ID: <e3067316-9c4e-bdb8-39db-bc4a9c29ca15@RedHat.com> (raw)
In-Reply-To: <877ew90z6j.fsf@notabene.neil.brown.name>
On 10/05/2017 10:48 PM, NeilBrown wrote:
>
> Both auth-rpcgss-module and rpc-statd-notify only
> ever need to be run once - the effect they have
> is permanent.
> We can give this information to systemd by setting
> RemainAfterExit=yes
> This avoids the minor cost of running them a second time
> if something "Wants" either service after it was first run,
> (e.g. both client and server startup can Want these),
> and avoids systemd complaining that it restarts to fast
> if multiple Wants happen at nearly the same time.
>
> Signed-off-by: NeilBrown <neilb@suse.com>
Committed...
steved.
> ---
> systemd/auth-rpcgss-module.service | 1 +
> systemd/rpc-statd-notify.service | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/systemd/auth-rpcgss-module.service b/systemd/auth-rpcgss-module.service
> index 5241f7b5d58e..4548283377d0 100644
> --- a/systemd/auth-rpcgss-module.service
> +++ b/systemd/auth-rpcgss-module.service
> @@ -14,3 +14,4 @@ ConditionPathExists=/etc/krb5.keytab
> [Service]
> Type=oneshot
> ExecStart=/sbin/modprobe -q auth_rpcgss
> +RemainAfterExit=yes
> diff --git a/systemd/rpc-statd-notify.service b/systemd/rpc-statd-notify.service
> index 687fe31140c0..aad4c0d29efe 100644
> --- a/systemd/rpc-statd-notify.service
> +++ b/systemd/rpc-statd-notify.service
> @@ -13,3 +13,4 @@ PartOf=nfs-utils.service
> [Service]
> Type=forking
> ExecStart=-/usr/sbin/sm-notify
> +RemainAfterExit=yes
>
prev parent reply other threads:[~2017-10-12 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 2:48 [nfs-utils PATCH] Add RemainAfterExit to two services NeilBrown
2017-10-12 14:20 ` Steve Dickson [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=e3067316-9c4e-bdb8-39db-bc4a9c29ca15@RedHat.com \
--to=steved@redhat.com \
--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 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).