diff options
author | Niels de Vos <ndevos@redhat.com> | 2015-11-18 12:28:50 +0100 |
---|---|---|
committer | Raghavendra Bhat <raghavendra@redhat.com> | 2015-11-23 20:57:02 -0800 |
commit | 73527a122ceb50c47812f4d3f50faf0172697d6f (patch) | |
tree | 2e032daa89c3f64c50665f21893fdac2ccfa6219 /xlators/mount | |
parent | 89962044417e1d01a31dee72357d5ebcae0f44cb (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: 1283144
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: http://review.gluster.org/12641
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'xlators/mount')
0 files changed, 0 insertions, 0 deletions