ARCKILL(1)

πŸ’… ARCKILL(1) β€” the kill-y one, from User Commands πŸŽ€

okay bestie, sit down, we're doing arckill today and honestly? it's giving "boss energy". this is the ARC command that kills running jobs. no cap. periodt. πŸ¦‹


✨ NAME ✨

arckill β€” ARC Kill πŸ”₯


🌸 DESCRIPTION 🌸

πŸ“œ Usage:

arckill [OPTION...] [job ...]

The arckill command is used to kill running jobs. like, that's the whole vibe. you point it at jobs and they're gone. πŸ’€


🎯 Brokering and filtering:

  • -C, --computing-element=ce β€” only select jobs that were submitted to this computing element. it's the "yes i mean this cluster specifically" filter ✨
  • -s, --status=statusstr β€” only select jobs whose status is statusstr. basically "only the ones looking like this, thanks" πŸ’…
  • -a, --all β€” all jobs. ALL of them. the whole group chat. every single one. πŸ™ˆ
  • -r, --rejectmanagement=URL β€” skip jobs that are on a computing element with a given URL. it's the "not you, girl" of options 🚫

πŸŽ›οΈ Behaviour tuning:

  • -k, --keep β€” keep the files on the server (do not clean). like leaving the leftovers in the fridge. iconic behaviour, honestly πŸ“
  • -i, --jobids-from-file=filename β€” a file containing a list of jobIDs. let the file do the talking πŸ“„
  • -j, --joblist=filename β€” the file storing information about active jobs (default /builddir/.arc/jobs.dat). yes, that path. exactly that path. don't come for me πŸŽ€
  • --no-authentication β€” do not perform any authentication for opened connections 😳
  • --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. it said what it said. πŸ’œ

πŸͺ„ Other actions:

  • -P, --listplugins β€” list the available plugins πŸ“‹βœ¨

βš™οΈ Application Options:

  • -h, --help β€” Show help options. classic. the goat. 🐐
  • -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. pick your chaos level πŸ”Š
  • -v, --version β€” print version information πŸ“Œ

πŸ‘‘ EXTENDED DESCRIPTION πŸ‘‘

The arckill command kills a running job on an ARC enabled resource. 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. two ways in, same result, slay ✨

More than one jobid and/or jobname can be given. If several jobs were submitted with the same jobname all those jobs are killed. 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 jobs can be killed. it's giving "no survivors" energy fr fr πŸ’…

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. πŸ‘€

If the job was successfully killed the attempt to remove the job from the remote cluster will be made unless the --keep option was specified. Depending on functionality of service job killing procedure may take time and it may be impossible to clean job immediately. In that case arckill will report number of cleaned jobs smaller than processed ones. Cleaning of leftover jobs may be performed by running arcclean later. so like, don't panic if the numbers look sus, bestie 😭

heads up: killing and cleaning are two different girlies, and sometimes cleaning has to wait its turn. arcclean is your cleanup bestie for later. 🧹

πŸ“ 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. this file is basically the group chat roster of your jobs 🫢

πŸ’– 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 genuinely wanna hear it, no gatekeeping πŸ’Œ


APACHE LICENSE Version 2.0 πŸŽ€


🌈 SEE ALSO 🌈

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

like... the whole squad. go read them. iykyk πŸ“šπŸ’œ


that's the whole page, bestie! arckill version 7.2.0, September 2026 β€” go kill those jobs, you absolute icon. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from