ARCCAT(1)

πŸ’… arccat(1) β€” User Commands, bestie edition

okay so. welcome to arccat, aka ARC Catenate, living in section 1 of your manual, and she is giving main character energy. she's the ARC girlie who does cat for your jobs. let's get into it πŸŽ€


✨ NAME ✨

arccat β€” ARC Catenate. that's it, that's the name, and honestly? iconic. πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

🌸 Usage 🌸

arccat [OPTION...] [job ...]

the arccat command performs the cat command on the stdout, stderr or the grid manager's error log of the job. literally just reading files but make it ✨distributed✨


πŸ’– Brokering and filtering πŸ’–

  • -C, --computing-element=ce β€” only select jobs that were submitted to this computing element. one CE only, no gatecrashing πŸ’…
  • -s, --status=statusstr β€” only select jobs whose status is statusstr. picky queen behavior, we love
  • -a, --all β€” all jobs. every single one. the whole roster 🫢
  • -r, --rejectmanagement=URL β€” skip jobs that are on a computing element with a given URL. blocking that CE fr fr πŸ™ˆ

🧚 Behaviour tuning 🧚

  • -i, --jobids-from-file=filename β€” a file containing a list of jobIDs
  • -j, --joblist=filename β€” the file storing information about active jobs (default /builddir/.arc/jobs.dat)
  • --no-authentication β€” do not perform any authentication for opened connections. no cap, no auth
  • --x509-authentication β€” perform X.509 authentication for opened connections
  • --token-authentication β€” perform token authentication for opened connections
  • --systemca β€” force using CA certificates configuration provided by OpenSSL
  • --gridca β€” force using CA certificates configuration for Grid services (typically IGTF)
  • --anyca β€” force using CA certificates configuration for Grid services (typically IGTF) and one provided by OpenSSL

⭐ Other actions ⭐

  • -o, --stdout β€” show the stdout of the job (default)
  • -e, --stderr β€” show the stderr of the job
  • -l, --joblog β€” show the CE's error log of the job
  • -f, --file=filepath β€” show the specified file from job's session directory
  • -P, --listplugins β€” list the available plugins

🌈 Application Options 🌈

  • -h, --help β€” Show help options
  • -z, --conffile=filename β€” configuration file (default ~/.arc/client.conf)
  • -t, --timeout=seconds β€” timeout in seconds (default 20)
  • -d, --debug=debuglevel β€” FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG
  • -v, --version β€” print version information

πŸ”₯ EXTENDED DESCRIPTION πŸ”₯

the arccat command displays the stdout or stderr of running jobs. it can also display A-REX's error log of a job. and the way that you point at a job? two options, both valid: either the jobid that was returned by arcsub(1) at submission time, or its jobname if the job description that was submitted contained a jobname attribute. pick your fighter πŸ’–

More than one jobid and/or jobname can be given. and if several jobs were submitted with the same jobname? the stdout, stderr or A-REX error log of all those jobs are shown. yes, all of them, we're not leaving anyone out 🫢

If the --joblist option is used the list of jobs is read from a file with the specified filename. By specifying the --all option, the stdout, stderr or A-REX error log of all active jobs will be shown. go big or go home, bestie.

The --computing-element option can be used to select or reject jobs at specific CEs. The --status option can be used to select jobs in a specific state. These options can be repeated several times β€” stack 'em, queen πŸ‘‘. See arstat(1) for possible state values.

⚠️ important caveat, no skipping: only jobs where the stdout or stderr argument was given in the job description can display the contents of those files. if you didn't ask for them at submission time, they're simply not there. it's giving "you had to be there" πŸ’€

πŸŽ€ FILES πŸŽ€

  • ~/.arc/client.conf β€” Some options can be given default values by specifying them in the ARC client configuration file. By using the --conffile option a different configuration file can be used than the default.
  • ~/.arc/jobs.dat β€” This a local database of the user's active jobs. When a job is successfully submitted it is added to database and when it is removed from the remote CE it is removed from this list. This database is used as the list of all active jobs when the user specifies the --all option to the various NorduGrid ARC user interface commands. By using the --joblist option a different file can be used than the default.

πŸ’œ AUTHOR πŸ’œ

ARC software is developed by the NorduGrid Collaboration (http://www.nordugrid.org), please consult the AUTHORS file distributed with ARC. Please report bugs and feature requests to http://bugzilla.nordugrid.org

(they want your bug reports, bestie, they're literally asking πŸ™)


APACHE LICENSE Version 2.0


πŸ¦‹ SEE ALSO πŸ¦‹

arcclean(1), arccp(1), arcget(1), arcinfo(1), arckill(1), arcls(1), arcmkdir(1), arcproxy(1), arcrenew(1), arcresume(1), arcrm(1), arcstat(1), arcsub(1), arcsync(1), arctest(1)

the whole friend group, all in section 1, all slaying πŸ’…βœ¨


and that's the page, babes β€” this is arccat version 7.2.0, dated September 2026, and she ate. no crumbs. periodt. πŸ’–

πŸ“¦ where this page comes from