diff options
| author | Kaushal M <kaushal@redhat.com> | 2015-11-18 11:21:13 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2015-11-18 02:21:05 -0800 |
| commit | 23440a73bc348bbc3bb43ec397f0639ee45865fc (patch) | |
| tree | ce6ca7f887b22aa48f144dcf93c52e410eb9018e /extras/systemd/glusterd.service.in | |
| parent | dc3aa7524e4974f9d02465e2e5dd6ed9b6d319e1 (diff) | |
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 <kaushal@redhat.com>
Reviewed-on: http://review.gluster.org/12605
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Diffstat (limited to 'extras/systemd/glusterd.service.in')
| -rw-r--r-- | extras/systemd/glusterd.service.in | 1 |
1 files changed, 1 insertions, 0 deletions
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 |