Message-ID: <54F62994.9020203@RedHat.com>
Date: Tue, 03 Mar 2015 16:37:24 -0500
From: Steve Dickson <SteveD@redhat.com>
MIME-Version: 1.0
To: =?UTF-8?B?WmJpZ25pZXcgSsSZZHJ6ZWpld3NraS1Tem1law==?=
	<zbyszek@in.waw.pl>,
        Andrei Borzenkov <arvidjaar@gmail.com>
CC: 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
References: <1425407803-5278-1-git-send-email-steved@redhat.com> <20150303220657.6ba6011b@opensuse.site> <20150303191803.GK3058@in.waw.pl>
In-Reply-To: <20150303191803.GK3058@in.waw.pl>
Content-Type: text/plain; charset=utf-8
Sender: linux-nfs-owner@vger.kernel.org


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.... 

Thanks for the cycles! 

steved.