Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

condor_store_cred(1) [debian man page]

condor_store_cred(1)					      General Commands Manual					      condor_store_cred(1)

Name
       condor_store_cred securely - stash a password

Synopsis
       condor_store_cred [-help]

       condor_store_credadd[ -c | -u username] [-p password] [-n machinename] [-f filename]

       condor_store_creddelete[ -c | -u username] [-n machinename]

       condor_store_credquery[ -c | -u username] [-n machinename]

Description
       condor_store_credstores passwords in a secure manner. There are two separate uses of condor_store_cred:

	  1.  A  shared  pool  password  is needed in order to implement the  PASSWORD authentication method. condor_store_cred using the -coption
	  deals with the password for the implied  condor_pool@$(UID_DOMAIN) user name.

	  On a Unix machine, condor_store_cred with the -foption is used to set the pool password, as needed when used with the  PASSWORD  authen-
	  tication method. The pool password is placed in a file specified by the  SEC_PASSWORD_FILE configuration variable.

	  2. In order to submit a job from a Windows platform machine, or to execute a job on a Windows platform machine utilizing the run_as_own-
	  erfunctionality, condor_store_cred stores the password of a user/domain pair securely in the Windows registry. Using this  stored  pass-
	  word,  Condor  may act on behalf of the submitting user to access files, such as writing output or log files. Condor is able to run jobs
	  with the user ID of the submitting user. The password is stored in the same manner as the system does when setting or  changing  account
	  passwords.

       Passwords are stashed in a persistent manner; they are maintained across system reboots.

       The  addargument on the Windows platform stores the password securely in the registry. The user is prompted to enter the password twice for
       confirmation, and characters are not echoed. If there is already a password stashed, the old password will be overwritten by the new  pass-
       word.

       The deleteargument deletes the current password, if it exists.

       The queryreports whether the password is stored or not.

Options
       -c

	  Operations refer to the pool password, as used in the  PASSWORD authentication method.

       -f filename

	  For Unix machines only, generates a pool password file named filenamethat may be used with the  PASSWORD authentication method.

       -help

	  Displays a brief summary of command options.

       -n machinename

	  Apply the command on the given machine.

       -p password

	  Stores password, rather than prompting the user to enter a password.

       -u username

	  Specify the user name.

Exit Status
       condor_store_credwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright  (C)  1990-2012  Condor  Team,  Computer  Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012					      condor_store_cred(1)

Check Out this Related Man Page

condor_continue(1)					      General Commands Manual						condor_continue(1)

Name
       condor_continue continue - suspended jobs from the Condor queue

Synopsis
       condor_continue [-help -version]

       condor_continue[-debug]	[-pool	centralmanagerhostname[:portnumber]-name  scheddname][-addr "<a.b.c.d:port>"] cluster cluster.process user
       -constraint expression-all

Description
       condor_continuecontinues one or more suspended jobs from the Condor job queue. If the -nameoption is specified, the  named  condor_scheddis
       targeted for processing. Otherwise, the local condor_scheddis targeted. The job(s) to be continued are identified by one of the job identi-
       fiers, as described below. For any given job, only the owner of the job or one of the queue super users (defined by the	 QUEUE_SUPER_USERS
       macro) can continue the job.

Options
       -help

	  Display usage information

       -version

	  Display version information

       -pool centralmanagerhostname[:portnumber]

	  Specify a pool by giving the central manager's host name and an optional port number

       -name scheddname

	  Send the command to a machine identified by scheddname

       -addr <a.b.c.d:port>

	  Send the command to a machine located at "<a.b.c.d:port>"

       -debug

	  Causes debugging information to be sent to  stderr , based on the value of the configuration variable  TOOL_DEBUG

       cluster

	  Continue all jobs in the specified cluster

       cluster.process

	  Continue the specific job in the cluster

       user

	  Continue jobs belonging to specified user

       -constraint expression

	  Continue all jobs which match the job ClassAd expression constraint

       -all

	  Continue all the jobs in the queue

Exit Status
       condor_continuewill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Examples
       To continue all jobs except for a specific user:

       % condor_continue  -constraint 'Owner =!= "foo"'

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright  (C)  1990-2012  Condor  Team,  Computer  Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012						condor_continue(1)
Man Page