1CONDOR_HISTORY(1)               HTCondor Manual              CONDOR_HISTORY(1)
2
3
4

NAME

6       condor_history - HTCondor Manual
7
8       View log of HTCondor jobs completed to date
9
10
11

SYNOPSIS

13       condor_history [-help ]
14
15       condor_history [-name name] [-pool centralmanagerhostname[:portnumber]]
16       [-backwards ] [-forwards ] [-constraint expr] [-file filename]  [-user‐
17       log  filename]  [-format  formatString AttributeName] [-autoformat[:jl‐
18       hVr,tng]  ** *attr1 [attr2 ...]*]  [-l |  -long  |  -xml  |  -json**  ]
19       [-match | -limit  ** *number*] [**cluster | cluster.process | owner ]
20

DESCRIPTION

22       condor_history  displays  a  summary of all HTCondor jobs listed in the
23       specified history files. If no history files  are  specified  with  the
24       -file option, the local history file as specified in HTCondor's config‐
25       uration file ($(SPOOL)/history by default) is read. The default listing
26       summarizes  in  reverse  chronological order each job on a single line,
27       and contains the following items:
28
29          ID     The cluster/process id of the job.
30
31          OWNER  The owner of the job.
32
33          SUBMITTED
34                 The month, day, hour, and minute the job was submitted to the
35                 queue.
36
37          RUN_TIME
38                 Remote  wall  clock  time  accumulated  by the job to date in
39                 days, hours, minutes, and seconds, given as the  job  ClassAd
40                 attribute RemoteWallClockTime.
41
42          ST     Completion status of the job (C = completed and X = removed).
43
44          COMPLETED
45                 The time the job was completed.
46
47          CMD    The name of the executable.
48
49       If  a  job  ID  (in the form of cluster_id or cluster_id.proc_id) or an
50       owner is provided, output will be restricted to jobs with the specified
51       IDs and/or submitted by the specified owner. The -constraint option can
52       be used to display jobs that satisfy a specified boolean expression.
53
54       The history file is kept in chronological order, implying that new  en‐
55       tries are appended at the end of the file. As of Condor version 6.7.19,
56       the format of the history file is altered to enable faster  reading  of
57       the history file backwards (most recent job first). History files writ‐
58       ten with earlier versions of Condor, as well as those that have entries
59       of both the older and newer format need to be converted to the new for‐
60       mat. See the /man-pages/condor_convert_history manual page for  details
61       on converting history files to the new format.
62

OPTIONS

64          -help  Display usage information and exit.
65
66          -name name
67                 Query the named condor_schedd daemon.
68
69          -pool centralmanagerhostname[:portnumber]
70                 Use  the centralmanagerhostname as the central manager to lo‐
71                 cate  condor_schedd  daemons.  The  default  is  the  COLLEC‐
72                 TOR_HOST, as specified in the configuration.
73
74          -backwards
75                 List  jobs  in  reverse chronological order. The job most re‐
76                 cently added to the history file is first. This  is  the  de‐
77                 fault ordering.
78
79          -forwards
80                 List jobs in chronological order. The job most recently added
81                 to the history file is last. At least 4  characters  must  be
82                 given  to  distinguish this option from the -file and -format
83                 options.
84
85          -constraint expr
86                 Display jobs that satisfy the expression.
87
88          -attributes attrs
89                 Display only the given attributes when the -long o  ption  is
90                 used.
91
92          -since jobid or expr
93                 Stop  scanning  when the given jobid is found or when the ex‐
94                 pression becomes true.
95
96          -local Read from local history files even if there is a  SCHEDD_HOST
97                 configured.
98
99          -file filename
100                 Use the specified file instead of the default history file.
101
102          -userlog filename
103                 Display  jobs,  with  job information coming from a job event
104                 log, instead of from the default history file.  A  job  event
105                 log  does  not  contain  all  of the job information, so some
106                 fields in the normal output of condor_history will be blank.
107
108          -format formatString AttributeName
109                 Display jobs with a custom format. See the condor_q man  page
110                 -format option for details.
111
112          -autoformat[:jlhVr,tng]  attr1  [attr2 ...] or -af[:jlhVr,tng] attr1
113          [attr2 ...]
114                 (output option) Display attribute(s) or expression(s) format‐
115                 ted  in  a default way according to attribute types. This op‐
116                 tion takes an arbitrary number of attribute  names  as  argu‐
117                 ments, and prints out their values, with a space between each
118                 value and a newline character after the  last  value.  It  is
119                 like the -format option without format strings.
120
121                 It is assumed that no attribute names begin with a dash char‐
122                 acter, so that the next word that begins  with  dash  is  the
123                 start  of  the next option. The autoformat option may be fol‐
124                 lowed by a colon character and formatting qualifiers to devi‐
125                 ate the output formatting from the default:
126
127                 j print the job ID as the first field,
128
129                 l label each field,
130
131                 h print column headings before the first line of output,
132
133                 V  use  %V  rather  than %v for formatting (string values are
134                 quoted),
135
136                 r print "raw", or unevaluated values,
137
138                 , add a comma character after each field,
139
140                 t add a tab character before each field instead  of  the  de‐
141                 fault space character,
142
143                 n add a newline character after each field,
144
145                 g add a newline character between ClassAds, and suppress spa‐
146                 ces before each field.
147
148                 Use -af:h to get tabular values with headings.
149
150                 Use -af:lrng to get -long equivalent format.
151
152                 The newline and comma characters may not  be  used  together.
153                 The l and h characters may not be used together.
154
155          -l or -long
156                 Display job ClassAds in long format.
157
158          -limit Number
159                 Limit  the number of jobs displayed to Number. Same option as
160                 -match.
161
162          -match Number
163                 Limit the number of jobs displayed to Number. Same option  as
164                 -limit.
165
166          -xml   Display  job  ClassAds in XML format. The XML format is fully
167                 defined in the reference manual, obtained from  the  ClassAds
168                 web         page,         with        a        link        at
169                 http://htcondor.org/classad/classad.html.
170
171          -json  Display job ClassAds in JSON format.
172

EXIT STATUS

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

AUTHOR

178       HTCondor Team
179
181       1990-2021,  Center for High Throughput Computing, Computer Sciences De‐
182       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
183       under the Apache License, Version 2.0.
184
185
186
187
1888.8                              Jan 26, 2021                CONDOR_HISTORY(1)
Impressum