Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
According to https://fedoraproject.org/wiki/Packaging/SysVInitScript
nfs-utils init scripts need to be improved:
SERVICE:
nfs
nfslock
rpcgssd
rpcidmapd
rpcsvcgssd
1. if program is dead and /var/lock/subsys/$SERVICE file exists the correct exit status code is "2"
# service $SERVICE stop
# touch /var/lock/subsys/SERVICE
# service $SERVICE status ; echo $?
now: 3
expected: 2
2. init scripts should return code "4" if stopping service under
nonprivileged user
# service $SERVICE start
# su testuserqa -c 'service $SERVICE stop' ; echo $?
now: 1
expected: 4
3. init scripts should return code "4" if starting service under
nonprivileged user
# service $SERVICE stop
# su testuserqa -c 'service $SERVICE start' ; echo $?
now:
rpcidmapd, rpcgssd: 0
nfs, nfslock, rpcsvcgssd: 1
expected: 4
4. init script should return usage and exit code "2" for unknown argument:
# service $SERVICE nonexist
now: 3
expected: 2
5. try-restart action should be supported
6. force-reload action should be supported (if it makes sence)
*** Bug 596039 has been marked as a duplicate of this bug. ***
Comment 3RHEL Program Management
2010-05-26 14:36:47 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
If services rpcgssd and rpcsvcgssd are not configured, status action should return code "3"
# cat /etc/sysconfig/nfs
SECURE_NFS=no
# service rpcgssd status ; echo $?
6
now: 6
expected: 3
# service rpcsvcgssd status ; echo $?
6
now: 6
expected: 3
Moving to ASSIGNED
Created attachment 435575[details]
init scripts patch - only check $SECURE_NFS on start
I think we may need something like this patch. It makes it only check the $SECURE_NFS var on start command.
verified on rhel6-snapshot8 with the above patch,result is good:
# service rpcsvcgssd status ; echo $?
rpc.svcgssd is stopped
3
# service rpcgssd status ; echo $?
rpc.gssd is stopped
3
Created attachment 436004[details]
patch -- remove superfluous $SECURE_NFS checks from init scripts
Actually, it looks like we already check $SECURE_NFS in the start block of these init scripts. So we should be able to just remove those checks without adding them back.
I think we just need this patch.
Comment 21releng-rhel@redhat.com
2010-11-10 21:14:21 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.