GNUNET-CONFIG(1)

✨ GNUNET-CONFIG(1) ✨

okay bestie, welcome to the General Commands Manual page for gnunet-config 💅 — this one's a whole vibe, let's get into it 🫶

---

🌸 NAME 🌸

gnunet-config — manipulate GNUnet configuration files and provide information on how GNUnet was built ✨

---

🎀 SYNOPSIS 🎀

gnunet-config [-b BACKEND | --supported-backend=BACKEND] [-C | --cflags]
              [-c FILENAME | --config=FILENAME] [-F | --full]
              [-f | --filename] [-h | --help] [-j | --libs]
              [-L LOGLEVEL | --loglevel=LOGLEVEL]
              [-o OPTION | --option=OPTION] [-p | --prefix]
              [-r | --rewrite] [-S -|-list-sections]
              [-s SECTION | --section=SECTION]
              [-V VALUE | --value VALUE] [-v | --version]

---

💖 DESCRIPTION 💖

so gnunet-config is literally your little config goblin 🧚 — you can use it to read or modify GNUnet configuration files. iconic. but that's not all, no ma'am 💅 — it can also hand you the info you need to properly build applications on top of GNUnet, like appropriate values for CFLAGS or the installation prefix. it's giving "helpful queen" energy 👑

• -b BACKEND, --supported-backend=BACKEND — vibe-checks whether the specified BACKEND is supported by the current installation 🦋. the backend has to match the name of a plugin, e.g. "namestore_postgres" for the Postgres database backend of the "NAMESTORE" service. if the BACKEND is supported, gnunet-config returns a status code of 0 (success) — slay 💖 — otherwise 77 (unsupported) 😭. when this option is specified, no other options may be specified. and if you do specify it together with other options, gnunet-config will return a status code of 1 (error). not me getting in trouble with the status codes 💀
• -C, --cflags — prints an appropriate value for CFLAGS so you can compile applications on top of GNUnet ✨
• -c FILENAME, --config=FILENAME — use the configuration file FILENAME 📁
• -F, --full — write the full configuration, not just the deltas to the defaults. all of it, no crumbs left behind 👑
• -f, --filename — try to perform expansions as if the option values represent filenames (this will also be applied even if the option is not really a filename, jsyk 🙈)
• -h, --help — prints short help on options. the little "help me" button 🫶
• -j, --libs — prints an appropriate value for LIBS so you can compile applications on top of GNUnet 🔥
• -L LOGLEVEL, --loglevel=LOGLEVEL — use LOGLEVEL for logging 📝. valid values are DEBUG, INFO, WARNING and ERROR. choose your fighter ⭐
• -o OPTION, --option=OPTION — which configuration option should be accessed or edited. required to set a value ⚠️. if not given, all values of a given section will be printed in the format "OPTION = VALUE" 🌈
• -p, --prefix — prints GNUnet's installation prefix (for example /usr/local.) 📍
• -r, --rewrite — write the configuration to file, even if it did not change. stubborn queen behavior, honestly 💅
• -S, -, --list-sections — lists available configuration sections for use with --section 📜
• -s SECTION, --section=SECTION — which configuration section should be accessed or edited. required option ⚠️
• -V VALUE, --value VALUE — configuration value to store in the given section under the given option 💾. must only be given together with -s and -o options. trio or nothing, bestie 🫶
• -v, --version — prints the GNUnet version number 🔢

---

👀 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 ✨

info gnunet-c-tutorial

will give you access to a tutorial for developers 🧑‍💻 — yes, a whole tutorial, go off king

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⟩ 📧. please don't suffer in silence bestie, the devs wanna hear it 😭

---

and that's the whole page, bestie 💖 this one shipped from Debian and it's dated July 15, 2012 — old money, still iconic 👑✨ go forth and configure fr fr 🎀🦋💅