diff options
author | Niels de Vos <ndevos@redhat.com> | 2015-11-19 10:14:30 +0100 |
---|---|---|
committer | Niels de Vos <ndevos@redhat.com> | 2015-12-12 02:01:53 -0800 |
commit | b9bb39471ae75f5e1d6d697b6cb80e3d81da7484 (patch) | |
tree | eff3970475afd14e30ac115ddc7c7a25cb98220e | |
parent | c5f0ca5438d3b1234853e028c89f3ed6f894ef91 (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.
Cherry picked from commit 23440a73bc348bbc3bb43ec397f0639ee45865fc:
> 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>
Change-Id: Iee69965486be08711299aba235f7b00c3e2fe7e9
BUG: 1283542
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: http://review.gluster.org/12659
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
-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 fc8d8c9a235..39d1bffb7eb 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 |