linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: Systemd Mailing List <systemd-devel@lists.freedesktop.org>,
	Eric Work <work.eric@gmail.com>
Subject: Re: [PATCH] systemd: Have rpc-statd-notify.service Require network.target
Date: Thu, 19 Mar 2015 14:20:44 -0400	[thread overview]
Message-ID: <550B137C.5040509@RedHat.com> (raw)
In-Reply-To: <1425407803-5278-1-git-send-email-steved@redhat.com>



On 03/03/2015 01:36 PM, Steve Dickson wrote:
> Its been reported that having the rpc-statd-notify service
> depend on network.target instead network-online.target
> decrease boot times as much as 10 seconds on some
> installs
> 
> Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1183293
> 
> Signed-off-by: Steve Dickson <steved@redhat.com>
> Reported-by: Eric Work <work.eric@gmail.com>
Committed...

steved.

> ---
>  systemd/rpc-statd-notify.service |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/systemd/rpc-statd-notify.service b/systemd/rpc-statd-notify.service
> index a655445..b608a14 100644
> --- a/systemd/rpc-statd-notify.service
> +++ b/systemd/rpc-statd-notify.service
> @@ -1,6 +1,6 @@
>  [Unit]
>  Description=Notify NFS peers of a restart
> -Requires=network-online.target
> +Requires=network.target
>  After=network.target nss-lookup.target
>  
>  # if we run an nfs server, it needs to be running before we
> 

      parent reply	other threads:[~2015-03-19 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 18:36 [PATCH] systemd: Have rpc-statd-notify.service Require network.target Steve Dickson
2015-03-03 19:06 ` [systemd-devel] " Andrei Borzenkov
2015-03-03 19:18   ` Zbigniew Jędrzejewski-Szmek
2015-03-03 21:37     ` Steve Dickson
2015-03-03 22:51       ` Zbigniew Jędrzejewski-Szmek
2015-03-06 16:53         ` Steve Dickson
2015-03-19 18: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=550B137C.5040509@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=work.eric@gmail.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).