Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
just-man-pages/condor_cod(1)General Commands Manuajust-man-pages/condor_cod(1)

       condor_cod manage COD machines and jobs

       condor_cod [ -help -version ]

       condor_cod  request  [  -pool centralmanagerhostname[:portnumber] -name
       scheddname ][ -addr _a.b.c.d:port_ ]  [[	 -help	-version  ]  [	-debug
       -timeout	N -classad file	] ] [ -requirements expr ] [ -lease N ]

       condor_cod  release -id ClaimID [[ -help	-version ] [ -debug -timeout N
       -classad	file ] ] [ -fast ]

       condor_cod activate -id ClaimID [[ -help	-version ] [ -debug -timeout N
       -classad	 file ]	] [ -keyword string -jobad filename -cluster N -proc N
       -requirements expr ]

       condor_cod deactivate -id ClaimID [[ -help -version ] [ -debug -timeout
       N -classad file ] ] [ -fast ]

       condor_cod  suspend -id ClaimID [[ -help	-version ] [ -debug -timeout N
       -classad	file ] ]

       condor_cod renew	-id ClaimID [[ -help -version ]	[  -debug  -timeout  N
       -classad	file ] ]

       condor_cod  resume  -id ClaimID [[ -help	-version ] [ -debug -timeout N
       -classad	file ] ]

       condor_cod delegate_proxy -id ClaimID [[	 -help	-version  ]  [	-debug
       -timeout	N -classad file	] ] [ -x509proxy ProxyFile ]

       condor_cod  issues commands that	manage and use COD claims on machines,
       given proper authorization.

       Instead of specifying an	argument of request , release ,	activate , de-
       activate	 ,  suspend , renew , or resume	, the user may invoke the con-
       dor_cod tool by appending an underscore followed	by one of these	 argu-
       ments. As an example, the following two commands	are equivalent:

	   condor_cod release -id "<>#1073352104#4"

	   condor_cod_release -id "<>#1073352104#4"

       To  make	these extended-name commands work, hard	link the extended name
       to the condor_cod executable. For example on a Unix machine:

       ln condor_cod_request condor_cod

       The request argument gives a claim ID, and the other commands ( release
       ,  activate , deactivate	, suspend , and	resume ) use the claim ID. The
       claim ID	is given as the	last line of output for	a request  ,  and  the
       output appears of the form:

       ID of new claim is: "<a.b.c.d:portnumber>#x#y"

       An actual example of this line of output	is

       ID of new claim is: "<>#1073352104#4"

       The HTCondor manual has a complete description of COD.


	  Display usage	information


	  Display version information

       -pool centralmanagerhostname[:portnumber]

	  Specify  a pool by giving the	central	manager's host name and	an op-
	  tional 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_

       -lease N

	  For the request of a new claim, automatically	release	the claim  af-
	  ter N	seconds.


	  Create a new COD claim


	  Relinquish a claim and kill any running job


	  Start	a job on a given claim


	  Kill the current job,	but keep the claim


	  Suspend the job on a given claim


	  Renew	the lease to the COD claim


	  Resume the job on a given claim


	  Delegate an X509 proxy for the given claim

General	Remarks
Exit Status
       condor_cod  will	exit with a status value of 0 (zero) upon success, and
       it will exit with the value 1 (one) upon	failure.

       Center for High Throughput Computing, University	of Wisconsin-Madison

       Copyright (C) 1990-2015 Center for High Throughput Computing,  Computer
       Sciences	 Department, University	of Wisconsin-Madison, Madison, WI. All
       Rights Reserved.	Licensed under the Apache License, Version 2.0.

				     date	  just-man-pages/condor_cod(1)

Name | Synopsis | Description | Options | General Remarks | Examples | Exit Status | Author | Copyright

Want to link to this manual page? Use this URL:

home | help