ARCRESUME(1)

πŸ’– ARCRESUME(1) β€” the arcresume girlies' guide πŸ’–

okay bestie, welcome to arcresume β€” a User Commands classic, and honestly? she's serving. this is the manual page for arcresume, and i'm about to walk you through every single thing she does. no skips, no skimming, we're doing the whole thing. πŸŽ€


✨ NAME ✨

arcresume β€” aka ARC Resume. that's it, that's the name. short, sweet, iconic. πŸ‘‘


🌸 DESCRIPTION 🌸

πŸ¦‹ Usage πŸ¦‹

arcresume [OPTION...] [job ...]

that's the whole vibe. options, then jobs. periodt.


πŸ’… Brokering and filtering πŸ’…

this is where you get picky about which jobs you're messing with. filtering is self care, fr fr.

  • -C, --computing-element=ce β€” only pick the jobs that got submitted to this specific computing element. one CE only, bestie.
  • -s, --status=statusstr β€” only grab jobs whose status is statusstr. if their status isn't it, they're not it.
  • -a, --all β€” literally every job. all of them. the whole roster. πŸ‘‘
  • -r, --rejectmanagement=URL β€” skips any job that's sitting on a computing element with the URL you give. it's giving "not you, next". πŸ’€

🧚 Behaviour tuning 🧚

the little knobs and dials that change how she acts. very customizable, very main character.

  • -i, --jobids-from-file=filename β€” point her at a file that's got a list of jobIDs in it. she'll read them from there.
  • -j, --joblist=filename β€” the file that stores info about your active jobs. default is /builddir/.arc/jobs.dat.
  • --no-authentication β€” do not do any authentication on opened connections. none. zero. nada.
  • --x509-authentication β€” do X.509 authentication on opened connections.
  • --token-authentication β€” do token authentication on opened connections.
  • --systemca β€” force using the CA certificates config that OpenSSL provides.
  • --gridca β€” force using the CA certificates config for Grid services (typically IGTF).
  • --anyca β€” force using the CA certificates config for Grid services (typically IGTF) and the one OpenSSL provides. both. why choose. ✨

🌈 Other actions 🌈

  • -P, --listplugins β€” lists all the available plugins. show them off, queens. πŸ‘‘

⭐ Application Options ⭐

the standard-issue stuff. every tool's got them, but that doesn't make them less cute.

  • -h, --help β€” shows the help options. when in doubt, ask for help, bestie.
  • -z, --conffile=filename β€” the configuration file. default is ~/.arc/client.conf.
  • -t, --timeout=seconds β€” timeout, in seconds. default is 20.
  • -d, --debug=debuglevel β€” pick your debug level: FATAL, ERROR, WARNING, INFO, VERBOSE or DEBUG.
  • -v, --version β€” prints version info. know your queen's era. πŸ’–

πŸ”₯ EXTENDED DESCRIPTION πŸ”₯

so here's the actual tea: the arcresume command resumes a job that was submitted to an ARC CE. 🫢

you can refer to that job two ways:

  • by the jobid that arcsub(1) handed you back at submission time, or
  • by its jobname, if the job description you submitted had a jobname attribute in it.

and you're not limited to one! you can give more than one jobid and/or jobname. and listen β€” if several jobs were submitted with the same jobname, then all of those jobs get resumed. the whole squad. πŸ’…

if you use the --joblist option, the list of jobs gets read from a file with the filename you specify. and if you hit --all, every active job gets resumed. every last one. no cap.

the --computing-element option is how you select or reject jobs at specific clusters. the --status option is how you select jobs in a specific state. and here's the cute part β€” these options can be repeated several times. stack them, layer them, build a whole filter situation. 🌸

heads up: go check arcstat(1) for the possible state values, because that's where those live. iykyk.

πŸŽ€ FILES πŸŽ€

  • ~/.arc/client.conf β€” some options can be given default values by specifying them in the ARC client configuration file. and if you wanna use a different configuration file than the default one, that's what the --conffile option is for. πŸ’œ
  • ~/.arc/jobs.dat β€” this is a local database of the user's active jobs. when a job is successfully submitted it gets added to the database, and when it's removed from the remote CE it gets removed from this list. this database is what's used as the list of all active jobs when you specify the --all option to the various NorduGrid ARC user interface commands. and if you wanna use a different file than the default, use the --joblist option. πŸ¦‹

πŸ’œ AUTHOR πŸ’œ

ARC software is developed by the NorduGrid Collaboration (http://www.nordugrid.org). please consult the AUTHORS file distributed with ARC. and please report bugs and feature requests to http://bugzilla.nordugrid.org β€” they wanna hear from you, bestie. πŸ™ˆ


APACHE LICENSE Version 2.0


🌟 SEE ALSO 🌟

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

the whole friend group. go say hi. 🫢


and that's the page!! this was arcresume version 7.2.0, dated September 2026 β€” she's been serving since way back and she's still slaying. βœ¨πŸ’–βœ¨ mwah, go resume some jobs, you absolute icon. πŸ’…πŸŒˆ

πŸ“¦ where this page comes from