arckill man page
arckill — ARC Kill
The arckill command is used to kill running jobs.
arckill [options] [job ...]
- -a, --all
- -j, --joblist=filename
the file storing information about active jobs (default ~/.arc/jobs.xml)
- -i, --jobids-from-file=filename
a file containing a list of jobIDs
- -c, --cluster=name
select one or more computing elements: name can be an alias for a single CE, a group of CEs or a URL
- -r, --rejectmanagement=URL
skip jobs which are on a computing element with a given URL
- -s, --status=statusstr
only select jobs whose status is statusstr
- -k, --keep
keep files on the remote cluster (do not clean)
- -P, --listplugins
list the available plugins
- -t, --timeout=seconds
timeout in seconds (default 20)
- -z, --conffile=filename
configuration file (default ~/.arc/client.conf)
- -d, --debug=debuglevel
FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG
- -v, --version
print version information
- -?, --help
- job ...
list of jobids and/or jobnames
The arckill command kills a running job on an ARC enabled resource. The job can be referred to either by the jobid that was returned by arcsub(1) at submission time or by its jobname if the job description that was submitted contained a jobname attribute.
More than one jobid and/or jobname can be given. If several jobs were submitted with the same jobname all those jobs are killed. If the --joblist option is used the list of jobs is read from a file with the specified filename. By specifying the --all option, all jobs can be killed.
The --cluster option can be used to select or reject jobs at specific clusters. See arcsub(1) for a discussion of the format of arguments to this option. The --status option can be used to select jobs in a specific state. These options can be repeated several times. See arstat(1) for possible state values.
If the job was successfully killed the attepmt to remove the job from the remote cluster will be made unless the --keep option was specified. Depending on functionality of service job killing procedure may take time and it may be impossible to clean job immediately. In that case arckill will report number of cleaned jobs smaller than processed ones. Cleaning of leftover jobs may be performed by running arcclean later.
Some options can be given default values by specifying them in the ARC client configuration file. By using the --conffile option a different configuration file can be used than the default.
This a local list of the user's active jobs. When a job is successfully submitted it is added to this list and when it is removed from the remote cluster it is removed from this list. This list is used as the list of all active jobs when the user specifies the --all option to the various NorduGrid ARC user interface commands. By using the --joblist option a different file can be used than the default.
The location of the user's Grid proxy file. Shouldn't be set unless the proxy is in a non-standard location.
The location where ARC is installed can be specified by this variable. If not specified the install location will be determined from the path to the command being executed, and if this fails a WARNING will be given stating the location which will be used.
The location of ARC plugins can be specified by this variable. Multiple locations can be specified by separating them by : (; in Windows). The default location is $ARC_LOCATION/lib/arc (\ in Windows).
APACHE LICENSE Version 2.0
ARC software is developed by the NorduGrid Collaboration (http://www.nordugrid.org), please consult the AUTHORS file distributed with ARC. Please report bugs and feature requests to http://bugzilla.nordugrid.org
arccat(1), arcclean(1), arccp(1), arcget(1), arcinfo(1), arcls(1), arcmkdir(1), arcproxy(1), arcrenew(1), arcresub(1), arcresume(1), arcrm(1), arcstat(1), arcsub(1), arcsync(1), arctest(1)
arccat(1), arcclean(1), arcget(1), arcinfo(1), arcproxy(1), arcrenew(1), arcresub(1), arcresume(1), arcstat(1), arcsub(1), arcsync(1), arctest(1).