From 23440a73bc348bbc3bb43ec397f0639ee45865fc Mon Sep 17 00:00:00 2001 From: Kaushal M Date: Wed, 18 Nov 2015 11:21:13 +0530 Subject: glusterd.service: Ensure rpcbind is started before glusterd Having the rpcbind.service under the `After` option only ensures that glusterd.service is started after rpcbind.service if both are enabled/started at the same time. It doesn't ensure that starting glusterd.service will start rpcbind.service. The systemd.unit(5) man page suggests to use both the `Requires` and `After` options to ensure that rpcbind is started before glusterd, whenever glusterd is started. BUG: 1282915 Change-Id: Iee69965486be08711299aba235f7b00c3e2fe7e9 Signed-off-by: Kaushal M Reviewed-on: http://review.gluster.org/12605 Reviewed-by: Atin Mukherjee Reviewed-by: Anand Nekkunti Tested-by: Gluster Build System Tested-by: NetBSD Build System --- extras/systemd/glusterd.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'extras') diff --git a/extras/systemd/glusterd.service.in b/extras/systemd/glusterd.service.in index 5f962a6d2a4..26694cfc8ab 100644 --- a/extras/systemd/glusterd.service.in +++ b/extras/systemd/glusterd.service.in @@ -1,5 +1,6 @@ [Unit] Description=GlusterFS, a clustered file-system server +Requires=rpcbind.service After=network.target rpcbind.service Before=network-online.target -- cgit