Date: Tue, 3 Mar 2015 23:51:32 +0100
From: Zbigniew =?utf-8?Q?J=C4=99drzejewski-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
Message-ID: <20150303225132.GL3058@in.waw.pl>
References: <1425407803-5278-1-git-send-email-steved@redhat.com>
 <20150303220657.6ba6011b@opensuse.site>
 <20150303191803.GK3058@in.waw.pl>
 <54F62994.9020203@RedHat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <54F62994.9020203@RedHat.com>
Sender: linux-nfs-owner@vger.kernel.org

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