Red Hat Bugzilla – Bug 474570
Incorrect exit codes from nfs init script
Last modified: 2009-05-18 15:02:53 EDT
+++ This bug was initially created as a clone of Bug #431891 +++
Description of problem:
/etc/init.d/nfs start fails (exit with a non-zero exit code) if nfs is already
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a export entry in /etc/exports
2. Run /etc/init.d/nfs start
3. Run /etc/init.d/nfs start again
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [FAILED]
The LSB specification
states that start on an already started service should be considdered success,
and return exit code 0.
It appears this has already been fixed in Fedora. The initscript in
nfs-utils-1.1.0-6.fc8 adheres to LSB.
--- Additional comment from email@example.com on 2008-09-16 14:41:39 EDT ---
fixed in nfs-utils-1.0.9-34
In our case, a regression test does a 'service nfs stop' to ensure that no nfs daemon is running. If no daemon was running, the init script returns failure.
Fixed in nfs-utils-1.0.6-90.EL4
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.