Bug 524226

Summary: dumpconf init script collected problems LSB-compilant
Product: [Fedora] Fedora Reporter: Yulia Kopkova <ykopkova>
Component: s390utilsAssignee: Dan Horák <dan>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dan, dkovalsk
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-10 14:05:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 521669    

Description Yulia Kopkova 2009-09-18 13:12:45 UTC 
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"
Comment 1 Yulia Kopkova 2009-09-24 13:04:47 UTC 
(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
Comment 2 Bug Zapper 2009-11-16 12:36:48 UTC 
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
Comment 4 Dan Horák 2010-03-10 14:05:34 UTC 
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.