Tags:
create new tag
,
view all tags
<BODY> <H1>glite-ce-job-cancel</H1> Section: User Commands (1)<BR><A HREF="#index">Index</A> <HR> <A NAME="lbAB"> </A> <H2>NAME</H2> glite-ce-job-cancel - Cancels one or more jobs previously submitted to CREAM based CEs. <P> <A NAME="lbAC"> </A> <H2>SYNOPSIS</H2> <B>glite-ce-job-cancel [options] <jobId1> <jobId2> ... <jobIdn></B> <P> <A NAME="lbAD"> </A> <H2>DESCRIPTION</H2> The command glite-ce-job-cancel cancels jobs previously submitted, using the glite-ce-job-submit command, to CREAM based CEs. <P> glite-ce-job-cancel can remove one or more jobs: the jobs to be removed are identified by their job identifiers (job Ids returned by the glite-ce-job-submit command) provided as arguments to the command and separated by a blank space. <P> It has to be remarked that a job can be cancelled only by his/her owner (i.e. the user who submitted it). Only the ``super-users'' can cancel jobs submitted by other persons. <BR> Before actually cancelling the specified jobs, the command prompts the user for confirmation. <P> <P> Job states for which cancellation is allowed are: <P> o Pending <P> o Idle <P> o Running <P> o Really-Running <P> o Held <P> For all the other job states the cancellation request will result in a failure. An error message is of course printed also if the specified jobId doesn't exist. <P> If the --all option is specified, all the jobs submitted to the interested CREAM CE (whose endpoint must be specified with the --endpoint option, which is mandatory in this case), owned by the user issuing the command, are removed. When the command is launched with the --all option, neither can a jobId be specified nor can the --input option be used. <P> <P> The --input option permits to specify a file (file_name) that contains the jobIds to be removed. This file must be the one generated with the --output option of the glite-ce-job-submit or glite-ce-job-list commands. When using this option the user is interrogated for choosing among all, one or a subset of the listed job identifiers. If the file file_name does not represent an absolute path the file will be searched in the current working directory. <P> <P> When a glite-ce-job-cancel request is issued, the host name and the port number to be used to contact the CREAM service(s) are retrieved from the specified jobIds (which encompass this information) unless the --endpoint option is used. As stated before, the --endpoint option is mandatory if the --all option is used. <P> <A NAME="lbAE"> </A> <H2>OPTIONS</H2> <DL COMPACT> <DT><B>--help, -h</B> <DD> Displays command usage. <P> <DT><B>--conf file_name, -c file_name</B> <DD> Specifies the user specific configuration file. <P> <DT><B>--all, -a</B> <DD> Cancels all known jobs in the specified (with the --endpoint option, which is mandatory in this case) CREAM CE, owned by the user issuing the command. This option can't be used either if one or more jobIds have been specified or if the --input option has been specified. <P> <DT><B>--endpoint host[:port], -e host[:port]</B> <DD> Selects the endpoint of the CREAM CE to send the cancel request to. If the port is not specified, the port to be used is the one specified in the CREAM UI configuration file. If this option is not specified, the endpoint will be extracted from the JobID strings. The endpoint must have the format <host>:<port> or <host>. <P> <DT><B>--donot-verify-ac-sign, -A</B> <DD> Allows the execution of the command even if the VO voms server certificate is not installed. <P> <DT><B>--input file_name, -i file_name</B> <DD> Cancels jobs whose Ids are contained in the file file_name. This option can't be used if the --all option has been specified as well. <P> <DT><B>--noint, -N</B> <DD> If this option is specified every interactive question to the user is skipped, and default values (yes; all: consider all jobs of the given list) will be considered. <P> <DT><B>--nomsg, -n</B> <DD> When this option is specified, any warning or info message is suppressed. <P> <DT><B>--debug, -d</B> <DD> When this option is specified, debugging information is displayed on the standard output and written also into the file glite-ce-job-cancel_CREAM_<username>_<date>_<time>.log file under (by default) the /tmp/glite_cream_cli_logs directory. <P> <P> <DT><B>--logfile file_name, -l file_name</B> <DD> When this option is specified, a command log file (whose pathname is file_name) is created. <P> <DT><B>--version, -v</B> <DD> Displays the version of the CREAM CLI software. <P> <P> </DL> <A NAME="lbAF"> </A> <H2>EXIT STATUS</H2> glite-ce-job-cancel exits with a value of 0 if the cancel operation succeeds, >0 if errors occurred. <P> <P> <A NAME="lbAG"> </A> <H2>EXAMPLES</H2> <P> glite-ce-job-cancel --input joblist.txt <BR> where joblist.txt is a file containing 2 jobIds, displays the following confirmation message: <P> 0. <A HREF="https://cream-ce-01.pd.infn.it:8443/CREAM116jbs5b9">https://cream-ce-01.pd.infn.it:8443/CREAM116jbs5b\ 9</A> <P> 1. <A HREF="https://cream-ce-01.pd.infn.it:8443/CREAM116jbi4o0">https://cream-ce-01.pd.infn.it:8443/CREAM116jbi4o\ 0</A> <P> a. Cancel all jobs <P> q. Quit <P> Your choice ? (multiple choices separated by ',') a <P> Are you sure you want to cancel specified job(s) [y/n]: y <P> <P> ---- <P> glite-ce-job-cancel --endpoint grid005.pd.infn.it:8443 --all <P> cancels all jobs, on the specified CREAM CE, owned by the user issuing the command. <BR> &\ nbsp; \  \ ; &nbs\ p; <A NAME="lbAH"> </A> <H2>SEE ALSO</H2> glite-ce-job-submit, glite-ce-job-list <P> <P> <P> <HR> <A NAME="index"> </A><H2>Index</H2> <DL> <DT><A HREF="#lbAB">NAME</A><DD> <DT><A HREF="#lbAC">SYNOPSIS</A><DD> <DT><A HREF="#lbAD">DESCRIPTION</A><DD> <DT><A HREF="#lbAE">OPTIONS</A><DD> <DT><A HREF="#lbAF">EXIT STATUS</A><DD> <DT><A HREF="#lbAG">EXAMPLES</A><DD> <DT><A HREF="#lbAH">SEE ALSO</A><DD> </DL> <HR> This document was created by <A HREF="/cgi-bin/man/man2html">man2html</A>, using the manual pages.<BR> Time: 12:36:11 GMT, May 02, 2011 </BODY> -- Main.MassimoSgaravatto - 2011-04-29
E
dit
|
A
ttach
|
PDF
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
M
ore topic actions
Topic revision: r2 - 2011-05-02
-
MassimoSgaravatto
Home
Site map
CEMon web
CREAM web
Cloud web
Cyclops web
DGAS web
EgeeJra1It web
Gows web
GridOversight web
IGIPortal web
IGIRelease web
MPI web
Main web
MarcheCloud web
MarcheCloudPilotaCNAF web
Middleware web
Operations web
Sandbox web
Security web
SiteAdminCorner web
TWiki web
Training web
UserSupport web
VOMS web
WMS web
WMSMonitor web
WeNMR web
General Doc
Functional Description
Batch System Support
CREAM and Information Service
Release Notes
Known Issues
Security in CREAM
Nagios Probes to monitor CREAM and WN
Papers
Presentations
User Doc
CREAM User Guide for EMI-1
CREAM User Guide for EMI-2
CREAM User Guide for EMI-3
CREAM JDL Guide
BLAH User Guide
Troubleshooting Guide
System Administrator Doc
System Administrator Guide for CREAM (EMI-3 release)
System Administrator Guide for CREAM (EMI-2 release)
System Administrator Guide for CREAM (EMI-1 release)
The CREAM configuration file
The CEMonitor configuration file
The CREAM CE Service Reference Card (EMI-2 release)
The CREAM CE Service Reference Card (EMI-1 release)
Batch System related documentation
Troubleshooting Guide
The guide for integrating EMIR in CREAM
]
Developers Doc
CREAM Client API C++ Documentation
CREAM Client API for Python
Other Doc
Contacts
Moving to CREAM from LCG-CE
Testing
Internal Collaboration Information
Credits
CREAM Web utilities
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback