Bug 76254 – 'rup' failure doesn't set return value

Bug 76254 - 'rup' failure doesn't set return value

Summary:	'rup' failure doesn't set return value

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rusers (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Phil Knirsch
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-10-18 15:02 EDT by Jay Turner
Modified:	2015-03-04 20:11 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-06-03 09:47:57 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jay Turner 2002-10-18 15:02:19 EDT

Description of Problem:
Executing 'rup bogushost' sets the return code to '0' and it should set it to
something non-zero.

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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Phil Knirsch 2004-04-15 09:39:52 EDT

The problem with this is that you can specify multiple hosts on the
commandline and there would be no way to figure out which one(s) failed.

And simply setting the exit code to 1 in case any of the hosts failed
isn't really helping a lot.

If you can give me a really good reason why this should be changed i
can certainly do it, but i don't see it.

Read ya, Phil

Comment 2 Jay Turner 2004-06-03 09:47:57 EDT

I'll buy that for a buck.  Closing out.

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