condor_tail(1)

Usage

condor_tail {[-help] | [-version]}

condor_tail [-pool centralmanagerhostname [:portnumber]] [-name name] [-debug] [-maxbytes numbytes] [-auto-retry] [-follow] [-no-stdout] [-stderr] job-ID [filename1] [filename2 ...]

Overview

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.

Options

-help: Display usage information and exit.

-version: Display version information and exit.

-pool centralmanagerhostname[:portnumber]: Specify a pool by giving the central manager's host name and an optional port number.

-name name: Query the condor_schedd daemon identified with name.

-debug: Display extra debugging information.

-maxbytes numbytes: Limits the maximum number of bytes transferred per tail access. If not specified, the maximum number of bytes is 1024.

-auto-retry: Retry the tail of the file(s) every 2 seconds, if the job is not yet running.

-follow: Repetitively tail the file(s), until interrupted.

-no-stdout: Do not tail stdout.

-stderr: Tail stderr instead of stdout.

Exit status

The exit status of condor_tail is zero on success.

History

Debian 13 (Trixie): the text shown here
Debian 10 (Buster)
Debian 9 (Stretch)
Debian 8 (Jessie)

-auto-retry since Debian 13 (Trixie); -debug since Debian 13 (Trixie); -follow since Debian 13 (Trixie); -help since Debian 13 (Trixie); -maxbytes since Debian 13 (Trixie); -name since Debian 13 (Trixie); -no-stdout since Debian 13 (Trixie); -pool since Debian 13 (Trixie); -stderr since Debian 13 (Trixie); -version since Debian 13 (Trixie).