1CONDOR_WHO(1) HTCondor Manual CONDOR_WHO(1)
2
6 condor_who - HTCondor Manual
7 Display information about owners of jobs and jobs running on an execute
9 machine
10
13 condor_who [help options ] [address options ] [display options ]
14
16 condor_who queries and displays information about the user that owns
17 the jobs running on a machine. It is intended to be run on an execute
18 machine.
19 The options that may be supplied to condor_who belong to three groups:
21 • Help options provide information about the condor_who tool.
23 • Address options allow destination specification for query.
25 • Display options control the formatting and which of the queried in‐
27 formation to display.
28 At any time, only one help option and one address option may be speci‐
30 fied. Any number of display options may be specified.
31 condor_who obtains its information about jobs by talking to one or more
33 condor_startd daemons. So, condor_who must identify the command port of
34 any condor_startd daemons. An address option provides this information.
35 If no address option is given on the command line, then condor_who
36 searches using this ordering:
37 1. A defined value of the environment variable CONDOR_CONFIG specifies
39 the directory where log and address files are to be scanned for
40 needed information.
41 2. With the aim of finding all condor_startd daemons, condor_who uti‐
43 lizes the same algorithm it would using the -allpids option. The
44 Linux ps or the Windows tasklist program obtains all PIDs. As Linux
45 root or Windows administrator, the Linux lsof or the Windows netstat
46 identifies open sockets and from there the PIDs of listen sockets.
47 Correlating the two lists of PIDs results in identifying the command
48 ports of all condor_startd daemons.
49
51 -help (help option) Display usage information
52 -daemons
54 (help option) Display information about the daemons running
55 on the specified machine, including the daemon's PID, IP ad‐
56 dress and command port
57 -diagnostic
59 (help option) Display extra information helpful for debugging
60 -verbose
62 (help option) Display PIDs and addresses of daemons
63 -address hostaddress
65 (address option) Identify the condor_startd host address to
66 query
67 -allpids
69 (address option) Query all local condor_startd daemons
70 -logdir directoryname
72 (address option) Specifies the directory containing log and
73 address files that condor_who will scan to search for command
74 ports of condor_start daemons to query
75 -pid PID
77 (address option) Use the given PID to identify the con‐
78 dor_startd daemon to query
79 -long (display option) Display entire ClassAds
81 -wide (display option) Displays fields without truncating them in
83 order to fit screen width
84 -format fmt attr
86 (display option) Display attribute attr in format fmt. To
87 display the attribute or expression the format must contain a
88 single printf(3)-style conversion specifier. Attributes must
89 be from the resource ClassAd. Expressions are ClassAd expres‐
90 sions and may refer to attributes in the resource ClassAd. If
91 the attribute is not present in a given ClassAd and cannot be
92 parsed as an expression, then the format option will be
93 silently skipped. %r prints the unevaluated, or raw values.
94 The conversion specifier must match the type of the attribute
95 or expression. %s is suitable for strings such as Name, %d
96 for integers such as LastHeardFrom, and %f for floating point
97 numbers such as LoadAvg. %v identifies the type of the attri‐
98 bute, and then prints the value in an appropriate format. %V
99 identifies the type of the attribute, and then prints the
100 value in an appropriate format as it would appear in the
101 -long format. As an example, strings used with %V will have
102 quote marks. An incorrect format will result in undefined
103 behavior. Do not use more than one conversion specifier in a
104 given format. More than one conversion specifier will result
105 in undefined behavior. To output multiple attributes repeat
106 the -format option once for each desired attribute. Like
107 printf(3)-style formats, one may include other text that will
108 be reproduced directly. A format without any conversion spec‐
109 ifiers may be specified, but an attribute is still required.
110 Include a backslash followed by an 'n' to specify a line
111 break.
112 -autoformat[:lhVr,tng] attr1 [attr2 ...] or -af[:lhVr,tng] attr1
114 [attr2 ...]
115 (display option) Display attribute(s) or expression(s) for‐
116 matted in a default way according to attribute types. This
117 option takes an arbitrary number of attribute names as argu‐
118 ments, and prints out their values, with a space between each
119 value and a newline character after the last value. It is
120 like the -format option without format strings.
121 It is assumed that no attribute names begin with a dash char‐
123 acter, so that the next word that begins with dash is the
124 start of the next option. The autoformat option may be fol‐
125 lowed by a colon character and formatting qualifiers to devi‐
126 ate the output formatting from the default:
127 l label each field,
129 h print column headings before the first line of output,
131 V use %V rather than %v for formatting (string values are
133 quoted),
134 r print "raw", or unevaluated values,
136 , add a comma character after each field,
138 t add a tab character before each field instead of the de‐
140 fault space character,
141 n add a newline character after each field,
143 g add a newline character between ClassAds, and suppress spa‐
145 ces before each field.
146 Use -af:h to get tabular values with headings.
148 Use -af:lrng to get -long equivalent format.
150 The newline and comma characters may not be used together.
152 The l and h characters may not be used together.
153
155 Example 1 Sample output from the local machine, which is running a sin‐
156 gle HTCondor job. Note that the output of the PROGRAM field will be
157 truncated to fit the display, similar to the artificial truncation
158 shown in this example output.
159 $ condor_who
161 OWNER CLIENT SLOT JOB RUNTIME PID PROGRAM
163 smith1@crane.cs.wisc.edu crane.cs.wisc.edu 2 320.0 0+00:00:08 7776 D:\scratch\condor\execut
164 Example 2 Verbose sample output.
166 $ condor_who -verbose
168 LOG directory "D:\scratch\condor\master\test/log"
170 Daemon PID Exit Addr Log, Log.Old
172 ------ --- ---- ---- ---, -------
173 Collector 6788 <128.105.136.32:7977> CollectorLog, CollectorLog.old
174 Credd 8148 <128.105.136.32:9620> CredLog, CredLog.old
175 Master 5976 <128.105.136.32:64980> MasterLog,
176 Match MatchLog, MatchLog.old
177 Negotiator 6600 NegotiatorLog, NegotiatorLog.old
178 Schedd 6336 <128.105.136.32:64985> SchedLog, SchedLog.old
179 Shadow ShadowLog,
180 Slot1 StarterLog.slot1,
181 Slot2 7272 <128.105.136.32:65026> StarterLog.slot2,
182 Slot3 StarterLog.slot3,
183 Slot4 StarterLog.slot4,
184 SoftKill SoftKillLog,
185 Startd 7416 <128.105.136.32:64984> StartLog, StartLog.old
186 Starter StarterLog,
187 TOOL TOOLLog,
188 OWNER CLIENT SLOT JOB RUNTIME PID PROGRAM
190 smith1@crane.cs.wisc.edu crane.cs.wisc.edu 2 320.0 0+00:01:28 7776 D:\scratch\condor\execut
191
193 condor_who will exit with a status value of 0 (zero) upon success, and
194 it will exit with the value 1 (one) upon failure.
195
197 HTCondor Team
198
200 1990-2023, Center for High Throughput Computing, Computer Sciences De‐
201 partment, University of Wisconsin-Madison, Madison, WI, US. Licensed
202 under the Apache License, Version 2.0.
203 Oct 02, 2023 CONDOR_WHO(1)