1condor_history(1)           General Commands Manual          condor_history(1)
2
3
4

Name

6       condor_historyView log of HTCondor jobs completed to date
7

Synopsis

9       condor_history[-help]
10
11       condor_history[-name  name] [-pool centralmanagerhostname[:portnumber]]
12       [-backwards] [-forwards] [-constraint expr] [-file filename]  [-userlog
13       filename] [-format formatString AttributeName] [-autoformat[:jlhVr,tng]
14       attr1 [attr2 ...]] [-l | -long | -xml | -json] [-match | -limit number]
15       [cluster | cluster.process | owner]
16

Description

18       condor_historydisplays  a  summary  of  all HTCondor jobs listed in the
19       specified history files. If no history files  are  specified  with  the
20       -fileoption, the local history file as specified in HTCondor's configu‐
21       ration file ($(SPOOL)/historyby default) is read. The  default  listing
22       summarizes  in  reverse  chronological order each job on a single line,
23       and contains the following items:
24
25       ID
26
27          The cluster/process id of the job.
28
29
30
31       OWNER
32
33          The owner of the job.
34
35
36
37       SUBMITTED
38
39          The month, day, hour, and minute the job was submitted to the queue.
40
41
42
43       RUN_TIME
44
45          Remote wall clock time accumulated by  the  job  to  date  in  days,
46          hours,  minutes,  and  seconds,  given  as the job ClassAd attribute
47          RemoteWallClockTime.
48
49
50
51       ST
52
53          Completion status of the job (C = completed and X = removed).
54
55
56
57       COMPLETED
58
59          The time the job was completed.
60
61
62
63       CMD
64
65          The name of the executable.
66
67
68
69       If a job ID (in the form  of  cluster_idor  cluster_id.proc_id)  or  an
70       owneris  provided, output will be restricted to jobs with the specified
71       IDs and/or submitted by the specified owner. The -constraintoption  can
72       be used to display jobs that satisfy a specified boolean expression.
73
74       The  history  file  is  kept  in chronological order, implying that new
75       entries are appended at the end of  the  file.  As  of  Condor  version
76       6.7.19,  the  format  of  the  history file is altered to enable faster
77       reading of the history file backwards (most recent job first).  History
78       files  written  with  earlier versions of Condor, as well as those that
79       have entries of both the older and newer format need to be converted to
80       the  new  format. See the condor_convert_historymanual page on page for
81       details on converting history files to the new format.
82

Options

84       -help
85
86          Display usage information and exit.
87
88
89
90       -name name
91
92          Query the named condor_schedddaemon.
93
94
95
96       -pool centralmanagerhostname[:portnumber]
97
98          Use the centralmanagerhostnameas the central manager to locate  con‐
99          dor_schedddaemons.  The  default is the COLLECTOR_HOST, as specified
100          in the configuration.
101
102
103
104       -backwards
105
106          List jobs in reverse chronological  order.  The  job  most  recently
107          added to the history file is first. This is the default ordering.
108
109
110
111       -forwards
112
113          List jobs in chronological order. The job most recently added to the
114          history file is last. At least 4 characters must be given to distin‐
115          guish this option from the -fileand -formatoptions.
116
117
118
119       -constraint expr
120
121          Display jobs that satisfy the expression.
122
123
124
125       -attributes attrs
126
127          Display only the given attributes when the -long option is used.
128
129
130
131       -since jobid or expr
132
133          Stop  scanning  when the given jobid is found or when the expression
134          becomes true.
135
136
137
138       -local
139
140          Read from local history files even if there is a SCHEDD_HOST config‐
141          ured.
142
143
144
145       -file filename
146
147          Use the specified file instead of the default history file.
148
149
150
151       -userlog filename
152
153          Display  jobs,  with  job  information  coming from a job event log,
154          instead of from the default history file. A job event log  does  not
155          contain  all  of  the  job information, so some fields in the normal
156          output of condor_historywill be blank.
157
158
159
160       -format formatStringAttributeName
161
162          Display jobs with a custom format. See the  condor_qman  page  -for‐
163          matoption for details.
164
165
166
167       -autoformat[:jlhVr,tng]   attr1  [attr2  ...]or  -af[:jlhVr,tng]  attr1
168       [attr2 ...]
169
170          (output option) Display attribute(s) or expression(s) formatted in a
171          default way according to attribute types. This option takes an arbi‐
172          trary number of attribute names as arguments, and prints  out  their
173          values,  with  a  space  between  each value and a newline character
174          after the last value. It is like the  -formatoption  without  format
175          strings.
176
177          It  is  assumed that no attribute names begin with a dash character,
178          so that the next word that begins with dash is the start of the next
179          option.  The  autoformatoption  may be followed by a colon character
180          and formatting qualifiers to deviate the output formatting from  the
181          default:
182
183          jprint the job ID as the first field,
184
185          llabel each field,
186
187          hprint column headings before the first line of output,
188
189          Vuse %V rather than %v for formatting (string values are quoted),
190
191          rprint "raw", or unevaluated values,
192
193          ,add a comma character after each field,
194
195          tadd  a tab character before each field instead of the default space
196          character,
197
198          nadd a newline character after each field,
199
200          gadd a newline  character  between  ClassAds,  and  suppress  spaces
201          before each field.
202
203          Use -af:hto get tabular values with headings.
204
205          Use -af:lrngto get -long equivalent format.
206
207          The  newline  and comma characters may notbe used together. The land
208          hcharacters may notbe used together.
209
210
211
212       -lor -long
213
214          Display job ClassAds in long format.
215
216
217
218       -limit Number
219
220          Limit the number of jobs displayed to Number. Same option as -match.
221
222
223
224       -match Number
225
226          Limit the number of jobs displayed to Number. Same option as -limit.
227
228
229
230       -xml
231
232          Display job ClassAds in XML format. The XML format is fully  defined
233          in the reference manual, obtained from the ClassAds web page, with a
234          link at http://htcondor.org/classad/classad.html.
235
236
237
238       -json
239
240          Display job ClassAds in JSON format.
241
242
243

Exit Status

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

Author

249       Center   for   High   Throughput   Computing,   University  of  Wiscon‐
250       sin–Madison
251

253       Copyright © 1990-2019 Center for High  Throughput  Computing,  Computer
254       Sciences  Department, University of Wisconsin-Madison, Madison, WI. All
255       Rights Reserved. Licensed under the Apache License, Version 2.0.
256
257
258
259                                     date                    condor_history(1)
Impressum