next up previous contents index
Next: condor_ checkpoint Up: 9. Command Reference Manual Previous: condor_ advertise   Contents   Index

Subsections


condor_ analyze

Display information about jobs in queue

Synopsis

condor_ analyze [-help]

condor_ analyze [-global] [-submitter submitter] [-name name] [-pool centralmanagerhostname[:portnumber]] [-long] [-run] [-expert] [{cluster | cluster.process | owner | -constraint expression ... } ]

Description

condor_ analyze displays analysis information about jobs in the Condor job queue. on a per machine basis. By default, condor_ analyze queries the local job queue, but this behavior may be modified.

Options

-global
Provides an analysis of all jobs in all queues. Note that this can be a lengthy analysis for large queues.
-submitter submittername
Does an analysis on all jobs of the given job submitter.
-help
Prints a short help screen and exits.
-name name
Restricts the analysis to jobs in the queue of given host name's condor_ schedd daemon.
-pool centralmanagerhostname[:portnumber]
Analyzes jobs in a specific pool by giving the central manager's host name and an optional port number. The default is given by the value of the COLLECTOR_HOST macro as specified in the configuration file.
-long
Requests a verbose output.
-expert
Displays shorter error messages.

To restrict the display to jobs of interest, a list of zero or more restrictions may be supplied. Each restriction may be one of:

cluster
Matches all jobs belonging to the specified cluster.
cluster.process
Matches jobs which belong to the specified cluster and have the specified process number.
owner
Matches all jobs owned by the specified owner.
-constraint expression
Matches all jobs that satisfy the specified ClassAd expression. (See section 4.1 for a discussion of ClassAd expressions.)

General Remarks

Although condor_ analyze provides a very good first approximation, the analyzer cannot diagnose all possible situations because the analysis is based on instantaneous and local information. Therefore, there are some situations (such as when several submitters are contending for resources, or if the pool is rapidly changing state) which cannot be accurately diagnosed.

Examples

Exit Status

condor_ analyze will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author

Condor Team, University of Wisconsin-Madison

Copyright

Copyright © 1990-2003 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. No use of the Condor Software Program is authorized without the express consent of the Condor Team. For more information contact: Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

See the Condor Version 6.6.0 Manual for additional notices.


next up previous contents index
Next: condor_ checkpoint Up: 9. Command Reference Manual Previous: condor_ advertise   Contents   Index
condor-admin@cs.wisc.edu