Description of problem: According to https://fedoraproject.org/wiki/FCNewInit/Initscripts there are several issues with fcoe-utils initscript: PROBLEM 1: Status after amtu is stopped returns 1, should be 3 PROBLEM 2: Status after amtu is not running but lock file exists returns 0, should be 2 PROBLEM 3: Status after amtu is not running but pid file exists returns 0, should be 1 Version-Release number of selected component (if applicable): fcoe-utils-1.0.8-2.fc12 How reproducible: always Steps to Reproduce: PROBLEM 1: 1. service fcoe stop 2. service fcoe status; echo $? Actual results: 1 Expected results: 3 PROBLEM 2: 1. touch /var/lock/subsys/fcoe 2. service fcoe status; echo $? Actual results: 0 Expected results: 2 PROBLEM 3: 1. touch /var/run/fcoe.pid 2. service fcoe status; echo $? Actual results: 0 Expected results: 1
CORRECTION: In the bug report please s/amtu/fcoe
The issue has been fixed, new build is available.
Bug reopned as the pid file issue 3 still isn't fixed: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: PID file :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ PASS ] :: Running 'touch /var/run/fcoe.pid' :: [ FAIL ] :: Running 'service fcoe status' (Expected 1, got 2) :: [ LOG ] :: Duration: 1s :: [ LOG ] :: Assertions: 1 good, 1 bad :: [ FAIL ] :: RESULT: PID file
After a consultation the source of issue has been discovered. Closing again.