xrdmapc(1)

πŸ’… xrdmapc β€” the redirector gossip sesh

okay bestie, so this one is xrdmapc, and it lives in section 1 of the General Commands Manual β€” the "general commands" girlies, you know the vibe. she's a little utility that walks up to your XRootD redirector and asks it status / subscribers / paths questions. and she reports back. no cap. πŸŽ€


✨ NAME ✨

xrdmapc β€” query XRootD redirector (status/subscribers/paths)

like, literally what it says on the tin. she queries the redirector. that's the whole job. πŸ¦‹

🌸 SYNOPSIS 🌸

xrdmapc [options] host:port [path]

options: [--format fmt] [--help] [--list args] [--quiet] [--verify]

so you give her a <host>:<port> (or just host:port, she's not picky about punctuation) and optionally a path. that's it. that's the whole invocation. ✨

πŸ’– DESCRIPTION πŸ’–

The xrdmapc utility queries the XRootD redirector (status/subscribers/paths). path, when specified, uses <host>:<port> to determine the locations of path and does optional verification.

ngl that's a lot of words for a small program but here's the translation: you point her at a redirector, she goes "okay and?" and then tells you where stuff lives. if you hand her a path too, she'll go find out which servers actually have it β€” and if you ask nicely with the verify flag, she'll check it for real. 🫢

πŸ‘‘ OPTIONS πŸ‘‘

  • -f | --format [text|json] β€” picks the output format, periodt. 'text' prints human-readable output (and yes, that's the default), while 'json' prints a JSON representation of the cluster topology. and here's the tea: in JSON output, the managers and servers arrays are sorted by name. so no, they're not in the order the redirector felt like telling you. πŸ’…
  • -l | --list [all|m|s] β€” what are we listing today, bestie? 'all' lists managers and servers (default, obviously), 'm' lists only managers, and 's' lists only servers. choose your fighter. 🌈
  • -q | --quiet β€” does not print error messages to cerr; errors appear inline instead. so like, she still tells you, just not by screaming into the stderr void. 😌
  • -r | --refresh β€” does not use cached information but will refresh the cache. she's not gonna trust the stale gossip, she's going to the source. icon behaviour, honestly. πŸ”₯
  • -v | --verify β€” verifies <path> existence status at each server. yes, each one. she's thorough like that. ✨

and if you scrolled back up to the synopsis and clocked a --help sitting in that options line β€” yeah, she's there. πŸŽ€

πŸ¦‹ NOTES πŸ¦‹

Documentation for all components associated with xrdcp can be found at https://xrootd.org/docs.html

(and yes, it says xrdcp in the original notes. that's not a typo i introduced, that's just how it's written, and we respect the source. πŸ’œ)

πŸ’€ DIAGNOSTICS πŸ’€

Errors yield an error message and a non-zero exit status. so if something's wrong, you get words and a weird number. that's how you know. 🫢

πŸ“ LICENSE πŸ“

LGPL

free as in ✨freedom✨, bestie.

πŸ’œ SUPPORT LEVEL πŸ’œ

The xrdmapc command is supported by the xrootd collaboration. Contact information can be found at:

https://xrootd.org/contact.html

they're nice, they'll help you. go say hi. 🧚


okay that's the whole page, you ate that. this was xrdmapc(1), from v6.2.0, and if anyone asks β€” you read the manual. mwah. πŸ’–πŸ’…πŸŽ€

πŸ“¦ where this page comes from