GNUNET-ARM(1)

πŸ’– GNUNET-ARM β€” control GNUnet services πŸ’–

okay bestie, sit down, hydrate, because we're about to learn how to boss around a whole pile of GNUnet services. this page is from the General Commands Manual, and it is lowkey iconic. πŸŽ€


✨ NAME ✨

gnunet-arm β€” control GNUnet services. that's it. that's the whole job. queen behavior. πŸ‘‘


🌈 SYNOPSIS 🌈

gnunet-arm [-c FILENAME | --config=FILENAME] [-d | --delete]
           [-e | --end] [-E | --no-stderr] [-h | --help]
           [-i SERVICE | --init=SERVICE] [-I | --info]
           [-k SERVICE | --kill=SERVICE]
           [-l FILENAME | --logfile=FILENAME]
           [-L LOGLEVEL | --loglevel=LOGLEVEL] [-m | --monitor]
           [-O | --no-stdout] [-q | --quiet] [-r | --restart]
           [-s | --start] [-T -DELAY | --timeout=TIMEOUT]
           [-v | --version]

like. look at her. all those little flags. she's giving ✨versatility✨. πŸ¦‹


πŸ’… DESCRIPTION πŸ’…

gnunet-arm can be used to start or stop GNUnet services, including the ARM service itself. and what IS the ARM service, you ask? bestie, ARM is literally the supervisor for GNUnet's service processes. think of her as the group chat admin who keeps everyone on task. 🌸

ARM starts services on-demand or as configured, and restarts them if they crash. no cap, she is that friend who notices when you go quiet and immediately checks on you. 🫢


πŸŽ€ the options (the whole menu, no skips, periodt) πŸŽ€

  • -c FILENAME, --config=FILENAME β€” use the configuration file FILENAME. your config, your rules. πŸ’–
  • -d, --delete β€” delete configuration file and directory on exit. it's giving "burn the evidence" energy, so be sure you actually mean it. πŸ”₯
  • -e, --end β€” shut down all GNUnet services, including ARM itself. and fr fr, running gnunet-arm -e is the usual way to shut down a GNUnet peer. this is the goodbye text, the close-friends-only farewell. 😭
  • -E, --no-stderr β€” don't let gnunet-arm inherit stderr (standard error). she said "I don't want those vibes, actually." πŸ™ˆ
  • -h, --help β€” print short help on options. when in doubt, ask her directly. ⭐
  • -i SERVICE, --init=SERVICE β€” starts the specified SERVICE if it's not already running. more specifically? this makes the service behave as if it were in the default services list. like adding someone to the main character roster. πŸ‘‘
  • -I, --info β€” list all running services. it's a headcount. who's here, who's thriving. 🌈
  • -k SERVICE, --kill=SERVICE β€” stop SERVICE if it's running. now listen carefully bestie, because this one has layers: while this will kill the service right now, the service may be restarted immediately if other services depend on it (the service is then started 'on-demand'). if the service used to be a 'default' service, its default-service status will be revoked. and if the service was not a default service, it will just be (temporarily) stopped, but could be re-started on-demand at any time. so yeah β€” you can end her but she might respawn. πŸ’€
  • -l FILENAME, --logfile=FILENAME β€” write logs to FILENAME. receipts, archived. πŸ“
  • -L LOGLEVEL, --loglevel=LOGLEVEL β€” use LOGLEVEL for logging. valid values are DEBUG, INFO, WARNING and ERROR. pick your drama level. πŸ’œ
  • -m, --monitor β€” monitor service activity of ARM. in this mode, the command will not terminate until the user presses CTRL-C (thus sending SIGTERM or SIGINT). so like, she's gonna watch. indefinitely. you're the one who has to say when. πŸ‘€
  • -O, --no-stdout β€” don't let gnunet-arm inherit standard output. mute the group chat, keep your peace. πŸ™ˆ
  • -q, --quiet β€” don't print status messages. sometimes silence is the loudest flex. 🀫
  • -r, --restart β€” stop and start all GNUnet default services. the classic "brb turning myself off and on again" move. πŸ”„
  • -s, --start β€” start all GNUnet default services on this system (and also ARM). naturally, if a service is demanded by a default service, it will then also be started. and yes β€” running gnunet-arm -s is the usual way to start a GNUnet peer. this is the "good morning, we're up" text. β˜€οΈ
  • -T -DELAY, --timeout=DELAY β€” exit with error status if operation does not finish after DELAY, provided in number of microseconds. yes, microseconds. tiny units. she does not have time to wait. ⏳
  • -v, --version β€” print GNUnet version number. the "what's your sign" of flags. ⭐

🌸 EXAMPLES 🌸

start the gnunet-arm for the user:

gnunet-arm -s

stop the gnunet-arm for the user:

$ gnunet-arm -e

see how the second one has the little $ in front? that's literally how it's written on the page. keeping it exactly, no edits, that's the rule. πŸ’–


πŸ¦‹ SEE ALSO πŸ¦‹

the full documentation for gnunet is maintained as a Texinfo manual. if the info(1) and gnunet programs are properly installed at your site, the command

info gnunet

should give you access to the complete handbook, and

info gnunet-c-tutorial

will give you access to a tutorial for developers. 🧚

depending on your installation, this information is also available in gnunet(7) and gnunet-c-tutorial(7).


πŸ’€ BUGS πŸ’€

report bugs by using https://bugs.gnunet.org or by sending electronic mail to ⟨gnunet-developers@gnu.org⟩. bestie, if something's broken, tell the devs, don't just suffer in silence. they want to know. 🫢


and that's the whole page, no skips, no cuts. πŸ’… this little icon shipped with Debian, from way back on January 4, 2012, and honestly she's aged like fine wine. stay slaying, stay supervised, and remember: ARM is watching so you don't have to. πŸŽ€βœ¨

bye bestie! πŸ’–