ScriptingClient(1)

πŸ‘‘ ScriptingClient(1) β€” it's giving "RSerPool client, but make it iconic"

okay bestie, so you've stumbled into the manual page for scriptingclient πŸ’… β€” it lives in section 1 of the General Commands Manual (the "general commands" shelf, where all the everyday baddies hang out). Sit down, grab a strawberry πŸ“, and let's get you fluent.


✨ NAME ✨

scriptingclient β€” the RSerPool Client (PU) for the Scripting service. No cap, that's the whole name. πŸŽ€


🌸 SYNOPSIS 🌸

scriptingclient [-poolhandle=pool_handle] [-environment=file_name]
                [-input=file_name] [-output=file_name] [-quiet]
                [-maxretry=trials] [-retrydelay=milliseconds]
                [-runid=description] [-transmittimeout=milliseconds]
                [-keepaliveinterval=milliseconds] [-keepalivetimeout=milliseconds]
                [-cspinterval=milliseconds]
                [-cspserver=address:port] [-logappend=filename]
                [-logcolor=on|off] [-logfile=filename] [-loglevel=0-9]

(that shot on the fence is just me being silly, the actual line is plain shell, don't @ me)


πŸ’– DESCRIPTION πŸ’–

so scriptingclient is a Reliable Server Pooling (RSerPool) pool user β€” a PU β€” built for the scripting service. and what does the scripting service do, you ask? πŸ¦‹ it literally takes your input data, hands it to a scripting PE, that PE runs a script doing some genuinely useful work on the input data, and then it sends output data back. that's it, that's the whole vibe.

like, for example? distributed simulation processing. imagine a simulation just getting passed around the pool like it's a snack at a sleepover. iconic behavior. πŸ”₯


πŸ’… ARGUMENTS πŸ’…

here's the menu, bestie β€” every single option, no gatekeeping:

  • -poolhandle=pool_handle β€” sets the PH to a non-default value. otherwise? the default setting is "ScriptingPool". you leave it alone, it stays "ScriptingPool". periodt.

🌈 Service Parameters 🌈

  • -environment=file_name β€” sets the name of the environment file to upload to the PE. and get this πŸ’œ β€” the PE may cache that environment file, which means it can skip uploading the same environment file again next time. lowkey efficiency queen.
  • -input=file_name β€” sets the name of the input file to upload to the PE.
  • -output=file_name β€” sets the name of the output file to write the download from the PE to.
  • -quiet β€” turns on quiet mode. i.e. only limited information is printed. shy main character energy πŸ™ˆ.
  • -maxretry=trials β€” maximum number of retries upon errors on the remote site. important detail fr fr: the error counter only increments when the remote-side script returns a non-zero error code. and when the error limit is reached, the received output file will be downloaded for debugging purposes. yes, debugging. it's giving detective. πŸ•΅οΈβ€β™€οΈ
  • -retrydelay=milliseconds β€” sets the retry delay upon failover, in milliseconds.
  • -runid=description β€” adds the given description to all log lines of the scripting service PU operation. super useful when multiple PUs are running simultaneously and you're like "wait which one is which 😭".
  • -transmittimeout=milliseconds β€” sets the transmission timeout, in milliseconds.
  • -keepaliveinterval=milliseconds β€” sets the keep-alive interval, in milliseconds.
  • -keepalivetimeout=milliseconds β€” sets the keep-alive timeout, in milliseconds.

⭐ ASAP Protocol Parameters ⭐

  • -registrar=address:port β€” adds a static PR entry into the Registrar Table. and yes, it is possible to add multiple entries. stack 'em up bestie 🫢.
  • -registrarannouncetimeout=milliseconds β€” sets the timeout for ASAP announces via multicast.
  • -registrarconnecttimeout=milliseconds β€” sets the timeout for ASAP connection establishment.
  • -registrarconnectmaxtrials=trials β€” sets the maximum number of ASAP connection establishment trials.
  • -registrarrequesttimeout=milliseconds β€” sets the timeout for ASAP requests.
  • -registrarresponsetimeout=milliseconds β€” sets the timeout for waiting to receive ASAP responses.
  • -registrarrequestmaxtrials=trials β€” sets the maximum number of ASAP request trials.

πŸ¦‹ Component Status Protocol (CSP) Parameters πŸ¦‹

  • -cspinterval=milliseconds β€” sets the interval for the CSP status updates, in milliseconds. by default, the content of the environment variable CSP_INTERVAL is used. and if that's not defined? no CSP status reports will be sent. zero. nada. πŸ’€
  • -cspserver=address:port β€” sets the address of a CSP monitor server. by default, the content of the environment variable CSP_SERVER is used. and if that's not defined? again β€” no CSP status reports will be sent.

πŸŽ€ Logging Parameters πŸŽ€

  • -logappend=filename β€” writes logging output to a file (default is stdout); the output will be appended to the given file. not overwritten, appended. know the difference, it matters πŸ’–.
  • -logcolor=on|off β€” turns ANSI colorization of the logging output on or off. pick your fighter: on or off.
  • -logfile=filename β€” writes logging output to a file (default is stdout); the given file will be overwritten. bestie. OVERWRITTEN. ⚠️ don't say i didn't warn you.
  • -loglevel=0-9 β€” sets the logging verbosity from 0 (none) to 9 (very verbose). and a genuine recommendation here, not a vibe: it is recommended to use at least a value of 2 so you can actually see possibly important error messages and warnings. you want to know when things break, fr fr πŸ”₯.

🌱 ENVIRONMENT 🌱

scriptingclient 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 environment tea. 🍡


πŸ‘‘ DIAGNOSTICS πŸ‘‘

if loglevel>0, log messages will be printed to stdout or into a specified log file. simple as that, no plot twist. ✨


πŸ”— 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/

go read them, i know you want to, it's giving academic slay πŸ“šπŸ’œ


🌟 and that's the page, bestie! this whole thing came from the Scripting Client source, dated September 21, 2025 β€” it's section 1 of the General Commands Manual, and you just read it all. obsessed with you for that. bye pookie, go run something πŸ’…πŸŽ€πŸ¦‹
πŸ“¦ where this page comes from