[Gluster-users] Gluster3.7 version of glusterd doesn't create a lock file in RHEL7.1
SATHEESARAN
sasundar at redhat.com
Sat May 16 08:00:48 UTC 2015
On 05/16/2015 01:25 PM, Niels de Vos wrote:
> On Sat, May 16, 2015 at 12:42:17PM +0530, SATHEESARAN wrote:
>> Hi Niels,
>>
>> I have installed glusterfs-3.7 in RHEL 7.1 and noticed that starting
>> glusterd in RHEL7.1
>> doesn't create a lock file - /var/lock/subsys/glusterd
>> I have seen this lock file getting created while starting glusterd in
>> RHEL6.x
>>
>> Is this the problem or the expected in RHEL 7.1 ?
> The /var/lock/subsys/glusterd file is created and deleted by the
> SysV-init script. RHEL-7 uses systemd, and this lock file is not needed
> there. systemd maintains the state, init-script writers do not need to
> maintain /var/lock/subsys/... files any more.
>
> If you have any checks for this lock-file, you need to adapt your tests
> for systemd. I think something like "systemctl is-active glusterd" would
> return useful results for you.
>
> Cheers,
> Niels
Thanks for that information and it makes sense :)
ndevos++
-- sas
More information about the Gluster-users
mailing list