Bug 576712 - corosync returns negative return codes on exit
Summary: corosync returns negative return codes on exit
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: corosync
Version: 14
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Angus Salkeld
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 576713
TreeView+ depends on / blocked
 
Reported: 2010-03-24 21:45 UTC by Steven Dake
Modified: 2016-04-26 18:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 576713 (view as bug list)
Environment:
Last Closed: 2012-05-21 09:26:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
patch that has been committed upstream (1.57 KB, patch)
2010-04-07 05:19 UTC, Angus Salkeld
no flags Details | Diff

Description Steven Dake 2010-03-24 21:45:35 UTC
Description of problem:
corosync returns negative return codes on exit.  corosync should return 0 on success 1..254 on failure.

Version-Release number of selected component (if applicable):
corosync-1.2.1

How reproducible:
100%

Steps to Reproduce:
1.ctrl-c corosync -f
2.check return code
3.
  
Actual results:
-1 is returned in success

Expected results:
0 returned in success 1.254 returned in failures

Additional info:
change needs to be tested with init script - return value may alter init script.

Comment 1 Angus Salkeld 2010-03-25 00:26:13 UTC
patch posted to the ML

Comment 2 Angus Salkeld 2010-04-07 05:12:59 UTC
patch committed upstream.
http://marc.info/?l=openais&m=126947725023878&w=4

Comment 3 Angus Salkeld 2010-04-07 05:19:50 UTC
Created attachment 404838 [details]
patch that has been committed upstream

Comment 4 Bug Zapper 2010-07-30 11:11:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.