RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
"service nfslock force-reload" should not start the service if nfslock is not running.
As the LSB said "force-reload	cause the configuration to be reloaded if the service supports this, otherwise restart the service if it is running". But i find that the "force-reload" just acts the same as "restart" due to /etc/init.d/nfslock

Version-Release number of selected component (if applicable):
RHEL-6.6

How reproducible:
100%

Steps to Reproduce:
1.service nfslock stop
2.service nfslock force-reload
3.service nfslock status

Actual results:
[root@ibm-x3550m3-02 ~]# service nfslock stop
Stopping NFS statd: [  OK  ]
[root@ibm-x3550m3-02 ~]# service nfslock force-reload
Stopping NFS statd: [FAILED]
Starting NFS statd: [  OK  ]
[root@ibm-x3550m3-02 ~]# echo $?
0
[root@ibm-x3550m3-02 ~]# service nfslock status
rpc.statd (pid  25939) is running...
                          ^^^^^^^ should not start the service
[root@ibm-x3550m3-02 ~]# uname -r
2.6.32-504.el6.x86_64
[root@ibm-x3550m3-02 ~]# 


Expected results:
The "force-reload" does nothing when the nfs service is not running.

Additional info:
The same action on rhel7 not start the service if nfs-lock is not running

*** Bug 1192929 has been marked as a duplicate of this bug. ***

*** Bug 1192932 has been marked as a duplicate of this bug. ***

*** Bug 1192935 has been marked as a duplicate of this bug. ***

restart | force-reload | reload all do the same thing.