On 04/07/2017 11:07 AM, Steve Dickson wrote: > There has been an number startup problems where parts of > the NFS server fail to start due to DNS and other > parts of the network not be up. > > Reading the systemd.special it seems network.target is > a passive unit which does not wait and network-online.target > is an active unit which does not wait so that > should be used. > > Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1419351 > > Signed-off-by: Steve Dickson <steved@xxxxxxxxxx> Committed... steved. > --- > systemd/nfs-server.service | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/systemd/nfs-server.service b/systemd/nfs-server.service > index 5be5de6..7cf4ae0 100644 > --- a/systemd/nfs-server.service > +++ b/systemd/nfs-server.service > @@ -7,8 +7,8 @@ Wants=rpcbind.socket > Wants=rpc-statd.service nfs-idmapd.service > Wants=rpc-statd-notify.service > > -After= local-fs.target > -After= network.target proc-fs-nfsd.mount rpcbind.socket nfs-mountd.service > +After= local-fs.target network-online.target > +After= proc-fs-nfsd.mount rpcbind.socket nfs-mountd.service > After= nfs-idmapd.service rpc-statd.service > Before= rpc-statd-notify.service > > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
