condor_qedit(1) [debian man page]
condor_qedit(1) General Commands Manual condor_qedit(1) Name condor_qedit modify - job attributes Synopsis condor_qedit [-debug] [-n schedd-name] [-pool pool-name] {cluster | cluster.proc | owner | -constraint constraint}attribute-nameattribute- value... Description condor_qeditmodifies job ClassAd attributes of queued Condor jobs. The jobs are specified either by cluster number, job ID, owner, or by a ClassAd constraint expression. The attribute-valuemay be any ClassAd expression. String expressions must be surrounded by double quotes. Multiple attribute value pairs may be listed on the same command line. To ensure security and correctness, condor_qeditwill not allow modification of the following ClassAd attributes: * Owner * ClusterId * ProcId * MyType * TargetType * JobStatus Since JobStatus may not be changed with condor_qedit, use condor_holdto place a job in the hold state, and use condor_releaseto release a held job, instead of attempting to modify JobStatus directly. If a job is currently running, modified attributes for that job will not affect the job until it restarts. As an example, for PeriodicRe- move to affect when a currently running job will be removed from the queue, that job must first be evicted from a machine and returned to the queue. The same is true for other periodic expressions, such as PeriodicHold and PeriodicRelease . Options -debug Causes debugging information to be sent to stderr , based on the value of the configuration variable TOOL_DEBUG -n schedd-name Modify job attributes in the queue of the specified schedd -pool pool-name Modify job attributes in the queue of the schedd specified in the specified pool Examples % condor_qedit -name north.cs.wisc.edu -pool condor.cs.wisc.edu 249.0 answer 42 Set attribute "answer". % condor_qedit -name perdita 1849.0 In '"myinput"' Set attribute "In". % condor_qedit jbasney NiceUser TRUE Set attribute "NiceUser". % condor_qedit -constraint 'JobUniverse == 1' Requirements '(Arch == "INTEL") && (OpSys == "SOLARIS26") && (Disk >= ExecutableSize) && (VirtualMemory >= ImageSize)' Set attribute "Requirements". General Remarks A job's ClassAd attributes may be viewed with condor_q -long Exit Status condor_qeditwill 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 (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0. See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu September 2012 condor_qedit(1)
Check Out this Related Man Page
condor_rm(1) General Commands Manual condor_rm(1) Name condor_rm remove - jobs from the Condor queue Synopsis condor_rm [-help -version] condor_rm[-debug] [-forcex] [-pool centralmanagerhostname[:portnumber]-name scheddname][-addr "<a.b.c.d:port>"] cluster... clus- ter.process... user... -constraint expression... condor_rm[-debug] [-pool centralmanagerhostname[:portnumber]-name scheddname][-addr "<a.b.c.d:port>"] -all Description condor_rmremoves one or more jobs from the Condor job queue. If the -nameoption is specified, the named condor_scheddis targeted for pro- cessing. Otherwise, the local condor_scheddis targeted. The jobs to be removed are identified by one or more job identifiers, as described below. For any given job, only the owner of the job or one of the queue super users (defined by the QUEUE_SUPER_USERS macro) can remove the job. When removing a grid job, the job may remain in the ``X'' state for a very long time. This is normal, as Condor is attempting to communi- cate with the remote scheduling system, ensuring that the job has been properly cleaned up. If it takes too long, or in rare circumstances is never removed, the job may be forced to leave the job queue by using the -forcexoption. This forcibly removes jobs that are in the ``X'' state without attempting to finish any clean up at the remote scheduler. Options -help Display usage information -version Display version information -pool centralmanagerhostname[:portnumber] Specify a pool by giving the central manager's host name and an optional port number -name scheddname Send the command to a machine identified by scheddname -addr <a.b.c.d:port> Send the command to a machine located at "<a.b.c.d:port>" -debug Causes debugging information to be sent to stderr , based on the value of the configuration variable TOOL_DEBUG -forcex Force the immediate local removal of jobs in the 'X' state (only affects jobs already being removed) cluster Remove all jobs in the specified cluster cluster.process Remove the specific job in the cluster user Remove jobs belonging to specified user -constraint expression Remove all jobs which match the job ClassAd expression constraint -all Remove all the jobs in the queue General Remarks Use the -forcexargument with caution, as it will remove jobs from the local queue immediately, but can orphan parts of the job that are running remotely and have not yet been stopped or removed. Examples For a user to remove all their jobs that are not currently running: % condor_rm -constraint 'JobStatus =!= 2' Exit Status condor_rmwill 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 (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0. See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu September 2012 condor_rm(1)