This is the command arckill that can be run in the OnWorks free hosting provider using one of our multiple free online workstations such as Ubuntu Online, Fedora Online, Windows online emulator or MAC OS online emulator
PROGRAM:
NAME
arckill - ARC Kill
DESCRIPTION
The arckill command is used to kill running jobs.
SYNOPSIS
arckill [options] [job ...]
OPTIONS
-a, --all
all jobs
-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
print help
ARGUMENTS
job ...
list of jobids and/or jobnames
EXTENDED DESCRIPTION
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.
Use arckill online using onworks.net services