Contact
Impressum
Why this name?
pdf

ARCRENEW

NAME

arcrenew - ARC Proxy Renewal

DESCRIPTION

The arcrenew command is used for renewing the proxy of jobs that have been submitted to grid enabled resources.

SYNOPSIS

arcrenew [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

-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 arcrenew command renews the proxy of a job submitted 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 the proxies of all those jobs are renewed. If the --joblist option is used the list of jobs is read from a file with the specified filename. By specifying the --all option, the proxies of all active jobs will be renewed.

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.

FILES

~/.arc/client.conf

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.

~/.arc/jobs.xml

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.

ENVIRONMENT VARIABLES

X509_USER_PROXY

The location of the user’s Grid proxy file. Shouldn’t be set unless the proxy is in a non-standard location.

ARC_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.

ARC_PLUGIN_PATH

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).

COPYRIGHT

APACHE LICENSE Version 2.0

AUTHOR

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

SEE ALSO

arccat(1), arcclean(1), arccp(1), arcget(1), arcinfo(1), arckill(1), arcls(1), arcmkdir(1), arcproxy(1), arcresub(1), arcresume(1), arcrm(1), arcstat(1), arcsub(1), arcsync(1), arctest(1)

pdf
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

NO to software patents