Bug 456480 - condor_status -run -format vs condor_q -run -format
Summary: condor_status -run -format vs condor_q -run -format
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: 1.0
Hardware: All
OS: Linux
low
low
Target Milestone: Next Version
: ---
Assignee: Matthew Farrellee
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-24 00:56 UTC by Matthew Farrellee
Modified: 2012-10-19 16:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-19 16:58:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Condor 11 0 None None None 2012-10-19 12:08:22 UTC

Description Matthew Farrellee 2008-07-24 00:56:05 UTC 
"condor_status -run -format ..." works as you might expect, it prints out your
special format for all machines with running jobs. Great.

"condor_q -run -format ..." prints out a mixture of "condor_q -run" output and
"condor_q -constraint 'JobStatus==2' -format ..." output. Not great.

Is this intended, or should it be fixed? There is a clear workaround, use
"condor_q -constraint 'JobStatus==2' -format ...", but that's onerous. This also
happens with -hold, -goodput, and -io.
Note You need to log in before you can comment on or make changes to this bug.