HSDump(1)
π HSDump(1) β the handlespace dumper β¨
okay bestie, gather round, because this is hsdump, a little chaos goblin from the General Commands Manual family, and she is very good at exactly one thing: snooping on a RSerPool Registrar π
πΈ NAME πΈ
hsdump β dumps the handlespace of a RSerPool Registrar. that's it. that's the job. no cap π
β¨ SYNOPSIS β¨
hsdump [-address:port] [-cspserver=address:port]
[-cspinterval=milliseconds] [-logappend=filename]
[-logcolor=on|off] [-logfile=filename] [-loglevel=0-9]
like, she takes a bunch of optional stuff. she's low-maintenance in that way. queen behavior π
π¦ DESCRIPTION π¦
so here's the vibe: hsdump dumps the handlespace of a Reliable Server Pooling (RSerPool) Registrar (PR). how? she literally just claims to be a peer registrar and then requests the handlespace via ENRP. it's giving fake-it-till-you-make-it, but for network protocols π
β οΈ Handle with care! β no seriously bestie, the original says this and I am not editing the drama out. be careful with this one.
π ARGUMENTS π
The following options are available:
address:portβ the ENRP address and port of the target registrar. yes, both. she needs directions πΊοΈ
π Component Status Protocol (CSP) Parameters π
-cspinterval=millisecondsβ sets the interval for the CSP status updates, measured in milliseconds. by default she uses whatever's in the environment variableCSP_INTERVAL. and if that's not defined? no CSP status reports get sent at all. silence. nada. π«₯-cspserver=address:portβ sets the address of a CSP monitor server. by default she takes whatever's in the environment variableCSP_SERVER. if that's not defined either, wellβ¦ again, no CSP status reports will be sent. the monitor is getting ghosted π
π Logging Parameters π
-logappend=filenameβ write logging output to a file (default isstdout); the output will be appended to the given file. nothing gets deleted, we're just adding to the pile π§Ί-logcolor=on|offβ turns ANSI colorization of the logging outputonoroff. aesthetic choices only β¨-logfile=filenameβ write logging output to a file (default isstdout); the given file will be overwritten. rip whatever was in there before, she is not gentle π-loglevel=0-9β sets the logging verbosity from0(none) all the way to9(very verbose). and fr fr, use at least2if you want to actually see the possibly important error messages and warnings. trust, you want that π
π§ ENVIRONMENT π§
hsdump uses the environment variables CSP_SERVER and CSP_INTERVAL to define a CSP server to send reports to, in the specified interval. that's the whole setup, bestie, she's keeping it cute and configurable π
π DIAGNOSTICS π
If loglevel>0, log messages will be printed to stdout or into a specified log file. so if you set it above zero and you're seeing nothing, check where you pointed the output π
β SEE ALSO β
For a detailed introduction to RSerPool, see: https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf
Thomas Dreibholz's RSerPool Page: https://www.nntb.no/~dreibh/rserpool/
and that's the whole page, periodt π
this was Handlespace Dump, dated May 12, 2025, and it's the HSDump(1) manual β go dump a handlespace (carefully!!) and slay π«Άππ₯
π¦ where this page comes from
- ubuntu stonking: rsplib-tools 3.5.8-1 Β· GPL-3.0-or-later
- Copyright (C) 2002-2026 by Thomas Dreibholz
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms