ARCCLEAN(1)

✨ ARCCLEAN ✨

okay bestie, welcome to arcclean β€” the ARC Clean girlie πŸ’…. she's a User Commands page, she's iconic, and she's about to free up your computing resource. let's get into it 🫢


🌸 DESCRIPTION 🌸

πŸ’– Usage:

arcclean [OPTION...] [job ...]

so the whole vibe of arcclean is: it removes a job from the computing resource. that's it. that's the job. (pun fully intended 😭)


πŸŽ€ Brokering and filtering:

these are your "which jobs are we even talking about" flags, bestie:

  • -C, --computing-element=ce β€” only pick jobs that were submitted to this computing element, no others, periodt.
  • -s, --status=statusstr β€” only pick jobs whose status is statusstr. very picky, very demure ✨
  • -a, --all β€” literally all the jobs. every single one. the whole roster πŸ‘‘
  • -r, --rejectmanagement=URL β€” skip jobs that are on a computing element with a given URL. not those ones, thanks πŸ’€

πŸ¦‹ Behaviour tuning:

the "how do you want her to act" section:

  • -f, --force β€” remove the job from the local list of jobs even if the job is not found in the infosys. yeah, she'll do it anyway 😀
  • -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. risky girlie behaviour, but okay 🫣
  • --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. both. she said both πŸ’…

🌈 Other actions:

  • -P, --listplugins β€” list the available plugins. show me what you're working with ✨

⭐ Application Options:

  • -h, --help β€” Show help options. the classic "help me bestie" move.
  • -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. spill the tea, choose your level πŸ“
  • -v, --version β€” print version information.

πŸ’œ EXTENDED DESCRIPTION πŸ’œ

okay so here's the full story. The arcclean command removes a job from the computing element. Only jobs that have finished can be removed. important!! you can't just yank an in-flight job, that's not the move. πŸ™ˆ

The job can be referred to either by the jobid that was returned by arcsub(1) at submission time, or by its jobname if the job description that was submitted contained a jobname attribute.

More than one jobid and/or jobname can be given. If several jobs were submitted with the same jobname, all those jobs are removed. If the --joblist option is used, the list of jobs is read from a file with the specified filename. By specifying the --all option, all active jobs can be removed. yeah, ALL of them. main character energy πŸ‘‘

The --computing-element option can be used to select or reject jobs at specific clusters. The --status option can be used to select jobs in a specific state. These options can be repeated several times. See arcstat(1) for possible state values. (go check her out, she's got the receipts πŸ“‹)

The --force option removes the job from your local database of jobs even if the job can not be found in the remote information system. Jobs not appearing in the remote information system can also be removed from the local database by specifying the --status option with value Undefined. so there's two paths to the same slay, pick your fave πŸ’…


🧚 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.
ngl, ~/.arc/jobs.dat is lowkey the backbone of this whole operation. treat her with respect 🫢

πŸ‘‘ 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 built this. they're the moment. go tell them about your bugs, they actually want to know fr fr πŸ’–)


APACHE LICENSE Version 2.0


🌈 SEE ALSO 🌈

arccat(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, honestly. a whole squad of icons πŸŽ€)


and that's the page bestie!! this was arcclean version 7.2.0, dated September 2026 β€” yes she's from the future and yes she ate πŸ’…βœ¨ go clean those jobs, ily, bye!! πŸ¦‹πŸ’–

πŸ“¦ where this page comes from