From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Steve Dickson <SteveD@redhat.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
Systemd Mailing List <systemd-devel@lists.freedesktop.org>
Subject: Re: [systemd-devel] [PATCH] systemd: Have rpc-statd-notify.service Require network.target
Date: Tue, 3 Mar 2015 23:51:32 +0100 [thread overview]
Message-ID: <20150303225132.GL3058@in.waw.pl> (raw)
In-Reply-To: <54F62994.9020203@RedHat.com>
On Tue, Mar 03, 2015 at 04:37:24PM -0500, Steve Dickson wrote:
>
>
> On 03/03/2015 02:18 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Mar 03, 2015 at 10:06:57PM +0300, Andrei Borzenkov wrote:
> > Indeed. From the man page:
> > -m retry-time
> > Specifies the length of time, in minutes, to continue retry‐
> > ing notifications to unresponsive hosts. If this option is
> > not specified, sm-notify attempts to send notifications for
> > 15 minutes. Specifying a value of 0 causes sm-notify to
> > continue sending notifications to unresponsive peers until
> > it is manually killed.
> >
> > Notifications are retried if sending fails, the remote does
> > not respond, the remote's NSM service is not registered, or
> > if there is a DNS failure which prevents the remote's
> > mon_name from being resolved to an address.
> >
> > So rpc-statd-notify.service should be fine with being started before
> > the network is up at all.
> Right... that's the point... we want the service to fork and keep trying
> in the background....
...so like Andrei wrote, the dependency on network.target can be removed
(I wasn't sure if it was clear what I meant).
Zbyszek
next prev parent reply other threads:[~2015-03-03 22:51 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 [this message]
2015-03-06 16:53 ` Steve Dickson
2015-03-19 18:20 ` 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=20150303225132.GL3058@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=SteveD@redhat.com \
--cc=arvidjaar@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.org \
/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.