Linux Certif

Toute la documentation sur la certification Linux LPI

condor_reconfig

Name

condor_reconfig Reconfigure Condor daemons

Synopsis

condor_reconfig [ -help -version ] condor_reconfig [ -debug ] [ -name name name -addr <a.b.c.d:port> <a.b.c.d:port> ... ][ -all ] [ -subsystem master startd schedd collector negotiator kbdd quill ] [ -full ] condor_reconfig [ -debug ] [ -pool centralmanagerhostname[:portnumber] -name name ][ -addr <a.b.c.d:port> ] ... [ -all ] [ -subsystem master startd schedd collector negotiator kbdd quill ] [ -full ]

Description

condor_reconfig reconfigures all of the Condor daemons in accordance with the current status of the Condor configuration file(s). Once reconfiguration is complete, the daemons will behave according to the policies stated in the configuration file(s). The main exception is with the DAEMON_LISTvariable, which will only be updated if the condor_restart command is used. There are a few other configuration settings that can only be changed if the Condor daemons are restarted. Whenever this is the case, it will be mentioned in section on page which lists all of the settings used to configure Condor. In general, condor_reconfig should be used when making changes to the configuration files, since it is faster and more efficient than restarting the daemons. The command condor_reconfig with no arguments or with the -subsystem master option will cause the reconfiguration of the condor_master daemon and all the child processes of the condor_master . For security purposes (authentication and authorization), this command requires an administrator's level of access. Note that changes to the ALLOW_*and DENY_*configuration variables require the -full option. See section on page for further explanation.

Options

-help

Display usage information

-version

Display version information

-full

Perform a full reconfiguration. In addition to re-reading the configuration files, a full reconfiguration will clear cached DNS information in the daemons. Use this option only when the DNS information needs to be reinitialized.

-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 name

Send the command to a machine identified by name

name

Send the command to a machine identified by name

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

-all

Send the command to all machines in the pool

-subsystem master startd schedd collector negotiator kbdd quill

Send the command to the named daemon. Without this option, the command is sent to the condor_master daemon.

Exit Status

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

Examples

To reconfigure the condor_master and all its children on the local host:

% condor_reconfig To reconfigure only the condor_startd on a named machine:

% condor_reconfig -name bluejay -subsystem startd To reconfigure a machine within a pool other than the local pool, use the -pool option. 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 command. This command reconfigures the single machine named cae17 within the pool of machines that has condor.cae.wisc.edu as its central manager:

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

Author

Condor Team, University of Wisconsin-Madison

Copyright

Copyright (C) 1990-2009 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.4.2 Manual or http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu