Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

condor_set_shutdown(1) [debian man page]

condor_set_shutdown(1)					      General Commands Manual					    condor_set_shutdown(1)

Name
       condor_set_shutdown Set - a program to execute upon condor_mastershut down

Synopsis
       condor_set_shutdown [-help -version]

       condor_set_shutdown-exec      programname[-debug]      [-pool	 centralmanagerhostname[:portnumber]]	  [-name     hostnamehostname-addr
       "<a.b.c.d:port>""<a.b.c.d:port>"-constraint expression-all]

Description
       condor_set_shutdownsets a program (typically a script) to execute when the condor_masterdaemon shuts down. The -exec programnameargument is
       required,  and  specifies  the program to run. The string programnamemust match the string that defines	Name in the configuration variable
       MASTER_SHUTDOWN_<Name> in the condor_masterdaemon's configuration. If it does not match, the condor_masterwill log an error and ignore  the
       request.

       For  purposes of authentication and authorization, this command requires the  ADMINISTRATOR access level. See section 3.6.1on page for fur-
       ther explanation.

Options
       -help

	  Display usage information

       -version

	  Display version information

       -debug

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

       -pool centralmanagerhostname[:portnumber]

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

       -name hostname

	  Send the command to a machine identified by hostname

       hostname

	  Send the command to a machine identified by hostname

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

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

       <a.b.c.d:port>

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

       -constraint expression

	  Apply this command only to machines matching the given ClassAd expression

       -all

	  Send the command to all machines in the pool

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

Examples
       To have all condor_masterdaemons run the program /bin/rebootupon shut down, configure the condor_masterto contain a definition similar to:

       MASTER_SHUTDOWN_REBOOT = /sbin/reboot

       where  REBOOT is an invented name for this program that the condor_masterwill execute. On the command line, run

       % condor_set_shutdown  -exec reboot -all
       % condor_off -graceful -all

       where the string  reboot matches the invented name.

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_set_shutdown(1)

Check Out this Related Man Page

condor_checkpoint(1)					      General Commands Manual					      condor_checkpoint(1)

Name
       condor_checkpoint send - a checkpoint command to jobs running on specified hosts

Synopsis
       condor_checkpoint [-help -version]

       condor_checkpoint[-debug]  [-pool  centralmanagerhostname[:portnumber]]	[-name hostnamehostname-addr "<a.b.c.d:port>""<a.b.c.d:port>"-con-
       straint expression-all]

Description
       condor_checkpoint sends a checkpoint command to a set of machines within a single pool. This causes the startd daemon on each of the speci-
       fied  machines  to  take  a  checkpoint of any running job that is executing under the standard universe. The job is temporarily stopped, a
       checkpoint is taken, and then the job continues. If no machine is specified, then the command is sent to the machine that issued  the  con-
       dor_checkpoint command.

       The  command  sent  is  a periodic checkpoint. The job will take a checkpoint, but then the job will immediately continue running after the
       checkpoint is completed. condor_vacate, on the other hand, will result in the job exiting (vacating) after it produces a checkpoint.

       If the job being checkpointed is running under the standard universe, the job produces a checkpoint and then continues running on the  same
       machine.  If  the  job  is  running under another universe, or if there is currently no Condor job running on that host, then condor_check-
       pointhas no effect.

       There is generally no need for the user or administrator to explicitly run condor_checkpoint. Taking checkpoints of running Condor jobs	is
       handled automatically following the policies stated in the configuration files.

Options
       -help

	  Display usage information

       -version

	  Display version information

       -debug

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

       -pool centralmanagerhostname[:portnumber]

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

       -name hostname

	  Send the command to a machine identified by hostname

       hostname

	  Send the command to a machine identified by hostname

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

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

       <a.b.c.d:port>

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

       -constraint expression

	  Apply this command only to machines matching the given ClassAd expression

       -all

	  Send the command to all machines in the pool

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

Examples
       To send a condor_checkpoint command to two named machines:

       % condor_checkpoint   robin cardinal

       To send the condor_checkpointcommand to a machine within a pool of machines other than the local pool, use the -pooloption. The argument is
       the name of the central manager for the pool. Note that one or more machines within the pool must be specified as the targets for the  com-
       mand. This command sends the command to a the single machine named cae17within the pool of machines that has condor.cae.wisc.eduas its cen-
       tral manager:

       % condor_checkpoint  -pool condor.cae.wisc.edu -name cae17

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_checkpoint(1)
Man Page

Featured Tech Videos