Scroll to navigation

CONDOR_TAIL(1) HTCondor Manual CONDOR_TAIL(1)

NAME

condor_tail - HTCondor Manual

Display the last contents of a running job's standard output or file.

SYNOPSIS

condor_tail [-help | -version]

condor_tail [-pool hostname[:portnumber]] [-name scheddname] [-debug] [-maxbytes numbytes] [-auto-retry] [-follow] [-no-stdout] [-stderr] job-ID [filename ...]

DESCRIPTION

condor_tail displays the last bytes of a file in the sandbox of a running job identified by the command line argument job-ID. stdout is tailed by default. The number of bytes displayed is limited to 1024, unless changed by specifying the -maxbytes option. This limit is applied for each individual tail of a file; for example, when following a file, the limit is applied each subsequent time output is obtained.

If you specify filename, that name must be specifically listed in the job's transfer_output_files <href="../man-pages/condor_submit.html#transfer_output_files"> submit command.

OPTIONS

Display usage information and exit.
Display version information and exit.
Specify a pool by giving the central manager's host name and an optional port number.
Query the condor_schedd daemon identified with scheddname.
Display extra debugging information.
Limits the maximum number of bytes transferred per tail access. If not specified, the maximum number of bytes is 1024.
Retry the tail of the file(s) every 2 seconds, if the job is not yet running.
Repetitively tail the file(s), until interrupted.
Do not tail stdout.
Tail stderr instead of stdout.
The job identifier in the format cluster.proc or just cluster to tail the first job in the cluster.
Optional filename(s) to tail instead of stdout. Must be listed in transfer_output_files <href="../man-pages/condor_submit.html#transfer_output_files">.



GENERAL REMARKS

condor_tail is useful for monitoring the progress of running jobs without waiting for them to complete and transfer output files back.

The -follow option works similarly to tail -f on Unix systems, continuously displaying new output as the job writes it.

EXAMPLES

Tail stdout of job 123.0:

$ condor_tail 123.0


Tail stderr of job 123.0:

$ condor_tail -stderr 123.0


Follow stdout of job 123.0, updating every 2 seconds:

$ condor_tail -follow 123.0


Tail a specific output file from job 123.0:

$ condor_tail 123.0 output.log


Tail with increased byte limit:

$ condor_tail -maxbytes 4096 123.0


EXIT STATUS

0 - Success

1 - Failure

SEE ALSO

condor_submit <href="../man-pages/condor_submit.html">, condor_q <href="../man-pages/condor_q.html">, condor_ssh_to_job <href="../man-pages/condor_ssh_to_job.html">, condor_transfer_data <href="../man-pages/condor_transfer_data.html">

AVAILABILITY

Linux, MacOS, Windows

Author

HTCondor Team

Copyright

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.

May 12, 2026