Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 8691

Summary:	rup <arg> host1 host2 ... hostN doesn't sort by <arg>
Product:	[Retired] Red Hat Linux	Reporter:	James Baum <james.baum>
Component:	rusers	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.1
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-01-21 08:29:14 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:

Description James Baum 2000-01-21 08:02:54 UTC

rup(1) ignores the arguments -h, -l and -t (sort by hostname, load or
uptime) if it is given a list of hostnames. It doesn't sort at all then,
but just uses the list in the order given.
Only tested on x86, but I presume that applies to all platforms.

rpm -qvf `which rup`
rusers-0.15-6

Comment 1 james.baum 2000-01-21 08:29:59 UTC

Hmm, looks like a buglet in bugzilla as well.
My original short title was:
"rup <arg> host1 host2 ... hostN doesn't sort by <arg>"
 or to put it in html:
"rup &lt;arg&gt; host1 host2 ... hostN doesn't sort by &lt;arg&gt;"
Html problem...

Main point:
rup -h gamma beta alpha

should return
alpha up ...
beta  up ...
gamma up ...

but it returns
gamma up ...
beta  up ...
alpha up ...

Comment 2 Phil Knirsch 2001-06-06 13:04:10 UTC

This is not a bug. It simply processes the command line args in the order that
they were given, which is the expected behaviour.
If you need ordering simply use a pipe:

rup <arg> host1 host2 ... hostN | sort

which should return the wanted ordered list.

Read ya, Phil