condor_fetchlog(1) [debian man page]
condor_fetchlog(1) General Commands Manual condor_fetchlog(1) Name condor_fetchlog Retrieve - a daemon's log file that is located on another computer Synopsis condor_fetchlog [-help -version] condor_fetchlog[-pool centralmanagerhostname[:portnumber]] [-master -startd -schedd -collector -negotiator -kbdd] machine-namesubsys- tem[.extension] Description condor_fetchlogcontacts Condor running on the machine specified by machine-name, and asks it to return a log file from that machine. Which log file is determined from the subsystem[.extension]argument. The log file is printed to standard output. This command eliminates the need to remotely log in to a machine in order to retrieve a daemon's log file. For security purposes of authentication and authorization, this command requires an administrator's level of access. See section 3.6.1on page for more details about Condor's security mechanisms. The subsystem[.extension]argument is utilized to construct the log file's name. Without an optional .extension, the value of the configura- tion variable named subsystem_LOG defines the log file's name. When specified, the .extensionis appended to this value. Typical strings for the argument subsystemare as given as possible values of the predefined configuration variable $(SUBSYSTEM) . See the definition in section 3.3.1. Note that access to any additional logs can be enabled by simply specifying the path to each log in the con- figuration file with a configuration parameter named <NAME>_LOG , choosing an arbitrary unique name for each case. A value for the optional .extensionargument is typically one of the three strings: 1. .old 2. .slot<X> 3. .slot<X>.old Within these strings, <X> is substituted with the slot number. 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 -master Send the command to the condor_masterdaemon (default) -startd Send the command to the condor_startddaemon -schedd Send the command to the condor_schedddaemon -collector Send the command to the condor_collectordaemon -kbdd Send the command to the condor_kbdddaemon Examples To get the condor_negotiatordaemon's log from a host named head.example.com from within the current pool: condor_fetchlog head.example.com NEGOTIATOR To get the condor_startddaemon's log from a host named execute.example.com from within the current pool: condor_fetchlog execute.example.com STARTD This command requested the condor_startddaemon's log from the condor_master. If the condor_masterhas crashed or is unresponsive, ask another daemon running on that computer to return the log. For example, ask the condor_startddaemon to return the condor_master's log: condor_fetchlog -startd execute.example.com MASTER Exit Status condor_fetchlog will 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_fetchlog(1)
Check Out this Related Man Page
condor_reconfig(1) General Commands Manual condor_reconfig(1) Name condor_reconfig Reconfigure - Condor daemons Synopsis condor_reconfig [-help -version] condor_reconfig[-debug] [-pool centralmanagerhostname[:portnumber]] [-name hostnamehostname-addr "<a.b.c.d:port>""<a.b.c.d:port>"-con- straint expression-all] [-daemon daemonname] Description condor_reconfigreconfigures 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_LIST variable, which will only be updated if the condor_restartcommand is used. Other configuration variables that can only be changed if the Condor daemons are restarted are listed in section 3.3.1on page . In general, condor_reconfigshould be used when making changes to the configuration files, since it is faster and more efficient than restarting the daemons. The command condor_reconfigwith no arguments or with the -daemon masteroption will cause the reconfiguration of the condor_masterdaemon and all the child processes of the condor_master. For security purposes (authentication and authorization), this command requires an administrator's level of access. See section 3.6.1on page for further 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 -daemon daemonname Send the command to the named daemon. Without this option, the command is sent to the condor_masterdaemon. Exit Status condor_reconfigwill 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_masterand all its children on the local host: % condor_reconfig To reconfigure only the condor_startdon a named machine: % condor_reconfig -name bluejay -daemon startd To reconfigure a machine within a pool 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 command. This command reconfigures the single machine named cae17within the pool of machines that has condor.cae.wisc.eduas its central manager: % condor_reconfig -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_reconfig(1)