Description of problem: Description of problem: According to https://fedoraproject.org/wiki/FCNewInit/Initscripts dumpconf init script have some LSB-compilant problems: 1. status action should return code "3" for stopped service # service dumpconf stop # service dumpconf status ; echo $? now: 0 expected: 3 2. nonexist action should have returncode 3 and usage info: # service dumpconf nonexist ; echo $? now: 1 expected: 3 3. insufficient rights, there should be return code 4 # su testuserqa -c "service dumpconf restart"; echo $? now: 1 expected: 4 4. /var/lock/subsys/dumpconf should be created when service starts and if dumpconf is dead and /var/lock/subsys/dumpconf lock file exists then status action should return code "2". 5. dumpconf init script should also support "condrestart" actions. The reason of filling it is "InitScripts LSB compliance project"
(In reply to comment #0) > > 2. nonexist action should have returncode 3 and usage info: > # service dumpconf nonexist ; echo $? > now: 1 > expected: 3 > Update: 2. nonexist action should have return code "2" and usage info: # service dumpconf nonexist ; echo $? now: 1 expected: 2
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
dumpconf isn't any long-time running service but a mechanism to configure kernel dump feature on s390x. It's developed by IBM, documented by IBM and it wouldn't be wise to diverge from that.