Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
glite-ce-job-purgeSection: User Commands (1)Index NAMEglite-ce-job-purge - Cleans one or more jobs from CREAM based CEs. After this operation the purged jobs can't be managed anymore.SYNOPSISglite-ce-job-purge [options] <jobId1> <jobId2> ... <jobIdn>DESCRIPTIONThe command glite-ce-job-purge purges jobs from CREAM based CEs, i.e. any reference to these jobs is cancelled. Therefore after this operation it is not possible anymore to monitor (e.g. with the glite-ce-job-status command) or in some other way ``manage'' these jobs.glite-ce-job-purge can purge 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. Before actually purging the considered jobs, the user is asked for confirmation. It has to be remarked that a job can be purged only by his/her owner (i.e. the user who submitted it). Only the ``super-users'' can purge jobs submitted by other persons. Job states for which the purge is allowed are: o REGISTERED o DONE-OK o DONE-FAILED o ABORTED o CANCELLED For all the other job states the purge request will result in a failure. An error message is of course printed also if the specified jobId doesn't exist. If the --all option is specified, all the jobs submitted to the interested CREAM CE (whose endpoint must be specified with the --endpoint option), owned by the user issuing the command, are purged. When the command is launched with the --all option, neither can a jobId be specified nor can the --input option be used. 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. If the file file_name does not represent an absolute path, the file will be searched in the current working directory. When a glite-ce-job-purge 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. OPTIONS
EXIT STATUSglite-ce-job-purge exits with a value of 0 if the cancel operation succeeds, >0 if errors occurred.EXAMPLES
1. > glite-ce-job-purge --input joblist.txt
1. https://cream-ce-01.pd.infn.it:8443/CREAM116jbi4o0 a. Purge all jobs q. Quit Your choice ? (multiple choices separated by ',') a Are you sure you want to purge specified job(s) [y/n]: y
2. > glite-ce-job-purge --endpoint grid005.pd.infn.it:8443 --all --noint
SEE ALSOglite-ce-job-submit
IndexThis document was created by man2html, using the manual pages. Time: 11:02:28 GMT, May 05, 2011 -- MassimoSgaravatto - 2011-05-05 |