.\"Man page for condor_fetchlog 
.\"Generated by makeman on Sun Feb  1 21:58:28 2015
.TH condor_fetchlog  1 "February 2015"
.SH Name
.P
condor_fetchlog Retrieve \- a daemon's log file that is located on another computer 
.P

.SH Synopsis
condor_fetchlog [-help -version] 
.P
condor_fetchlog[-pool centralmanagerhostname[:portnumber]] [-master -startd -schedd -collector -negotiator -kbdd] machine-namesubsystem[.extension]
.P

.SH Description
.P
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. 
.P
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. 
.P
The subsystem[.extension]argument is utilized to construct the log file's name. Without an optional .extension, the value of the configuration variable named subsystem_LOG defines the log file's name. When specified, the .extensionis appended to this value. 
.P
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 configuration file with a configuration parameter named  <NAME>_LOG , choosing an arbitrary unique name for each case. 
.P
A value for the optional .extensionargument is typically one of the three strings: 
.IP "" 3
1.  .old 
.IP "" 3
2.  .slot<X> 
.IP "" 3
3.  .slot<X>.old Within these strings,  <X> is substituted with the slot number. 
.P
.SH Options
.P

.B -help
.IP "" 3
Display usage information 
.IP "" 3
.P
.B -version
.IP "" 3
Display version information 
.IP "" 3
.P
.B -pool centralmanagerhostname[:portnumber]
.IP "" 3
Specify a pool by giving the central manager's host name and an optional port number 
.IP "" 3
.P
.B -master
.IP "" 3
Send the command to the condor_masterdaemon (default) 
.IP "" 3
.P
.B -startd
.IP "" 3
Send the command to the condor_startddaemon 
.IP "" 3
.P
.B -schedd
.IP "" 3
Send the command to the condor_schedddaemon 
.IP "" 3
.P
.B -collector
.IP "" 3
Send the command to the condor_collectordaemon 
.IP "" 3
.P
.B -kbdd
.IP "" 3
Send the command to the condor_kbdddaemon 
.IP "" 3
.P

.SH Examples
To get the condor_negotiatordaemon's log from a host named  head.example.com from within the current pool: 
.P

.br
condor_fetchlog  head.example.com NEGOTIATOR
.P
To get the condor_startddaemon's log from a host named  execute.example.com from within the current pool: 
.P

.br
condor_fetchlog  execute.example.com STARTD
.P
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: 
.P


.br
condor_fetchlog  -startd execute.example.com MASTER
.P
.SH 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. 
.P
.SH Author
Condor Team, University of Wisconsin-Madison 
.SH 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. 
.P
See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu