Bug 783444 - restorecond seems to always return exit code = 0
Summary: restorecond seems to always return exit code = 0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: policycoreutils
Version: 5.8
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-20 12:57 UTC by Milos Malik
Modified: 2012-01-24 16:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-24 16:44:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Milos Malik 2012-01-20 12:57:04 UTC
Description of problem:


Version-Release number of selected component (if applicable):
policycoreutils-newrole-1.33.12-14.8.el5
policycoreutils-gui-1.33.12-14.8.el5
policycoreutils-1.33.12-14.8.el5

How reproducible:
always

Steps to Reproduce:
# restorecond --help
restorecond: invalid option -- -
restorecond [-d] [-v] 
# echo $?
0
# restorecond -h
restorecond: invalid option -- h
restorecond [-d] [-v] 
# echo $?
0
# restorecond -u
restorecond: invalid option -- u
restorecond [-d] [-v] 
# echo $?
0
# 

Actual results:
* exit code = 0 if executed with invalid option

Expected results:
* exit code > 0 if executed with invalid option

Comment 1 Daniel Walsh 2012-01-24 16:27:35 UTC
I have fixed this in rawhide and upstream.  I don't think it is worth back porting.

Comment 2 RHEL Program Management 2012-01-24 16:44:46 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.


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