|GNUNET-CONFIG(1)||General Commands Manual||GNUNET-CONFIG(1)|
manipulate GNUnet configuration files and provide
information on how GNUnet was built
gnunet-config can be used to read or
modify GNUnet configuration files. It can also provide informations to
properly build applications on top of GNUnet, like appropriate values for
CFLAGS or the installation prefix.
- Tests whether the specified BACKEND is supported by the current installation. The backend must 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 will return a status code of 0 (success), otherwise 77 (unsupported). When this option is specified, no other options may be specified. Specifying this option together with other options will cause gnunet-config to return a status code of 1 (error).
- Print an appropriate value for CFLAGS to compile applications on top of GNUnet.
- Use the configuration file FILENAME.
- Write the full configuration, not just the deltas to the defaults.
- Try to perform expansions as if the option values represent filenames (will also be applied even if the option is not really a filename).
- Print short help on options.
- Print an appropriate value for LIBS to compile applications on top of GNUnet.
- Use LOGLEVEL for logging. Valid values are DEBUG, INFO, WARNING and ERROR.
- 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".
- Print GNUnet's installation prefix (for example /usr/local.)
- Write the configuration to file, even if it did not change.
- List available configuration sections for use with --section.
- Which configuration section should be accessed or edited. Required option.
- Configuration value to store in the given section under the given option. Must only be given together with -s and -o options.
- Print GNUnet version number.
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
should give you access to the complete handbook,
will give you access to a tutorial for developers.
|July 15, 2012||Debian|