kdb(1) -- key database access tools
Elektra provides a universal and secure framework to store configuration parameters in a global, hierarchical key database.
The core is a small library implemented in C. The plugin-based framework fulfills many configuration-related tasks to avoid any unnecessary code duplication across applications while it still allows the core to stay without any external dependency. Elektra abstracts from cross-platform-related issues with an consistent API, and allows applications to be aware of other applications' configurations, leveraging easy application integration.
The man pages can also be viewed online at: https://doc.libelektra.org/api/current/html/pages.html
And the page you are currently reading at: https://doc.libelektra.org/api/current/html/md_doc_help_kdb.html
Concepts are in man page section 7 and are prefixed with
You should start reading elektra-introduction(7).
Tools are in man page section 1 and are prefixed with
You should start reading kdb-introduction(1).
Documentation of plugins is available using the
kdb list for a list of plugins.
Every core-tool has the following options:
--help: Show the man page.
--version: Print version info.
--profile <profile>: Use a different kdb profile, see below.
--color <when>: Print never/auto(default)/always colored output.
Most tools have the following options:
--verbose: Explain what is happening.
--quiet: Suppress non-error messages.
kdb utility reads its own configuration from three sources
within the KDB (key database):
- /sw/kdb/profile/ (for legacy configuration)
- /sw/elektra/kdb/#0/%/ (for empty profile)
- /sw/elektra/kdb/#0/profile/ (for current profile)
The last source where a configuration value is found, wins.
For example, to permanently change verbosity one can use:
kdb set /sw/elektra/kdb/#0/current/verbose 1: Be verbose for every tool.
kdb set /sw/elektra/kdb/#0/current/quiet 1: Be quiet for every tool.
Profiles allow users to change many/all configuration options of a tool
at once. It influences from where the KDB entries are read.
For example if you use:
kdb export -p admin system
It will read its format configuration from
If you want different configuration per user or directories, you should prefer
to use the
dir namespaces. Then the correct configuration will
be chosen automatically according to the current user or current working directory.
Sometimes it is useful to start with default options, for example it is not
possible to invert the
In such situations one can simply select a non-existing profile, then
works as usual:
kdb mount -p nonexist -q /abc dir/abc
Elektra recommends to use rather long paths because it ensures flexibility in the future (e.g. to use profiles and have a compatible path for new major versions of configuration).
Long paths are, however, cumbersome to enter in the CLI.
Thus one can define bookmarks. Bookmarks are keys whose key name starts with
They are only recognized by the
kdb tool or tools that explicit have
support for it. Your applications should not depend on the presence of a
Bookmarks are stored below:
For every key found there, a new bookmark will be introduced.
Bookmarks can be used to start key names by using
+ (plus) as first character.
The string until the first
/ will be considered as bookmark.
For example, if you set the bookmark kdb:
kdb set user/sw/elektra/kdb/#0/current/bookmarks kdb set user/sw/elektra/kdb/#0/current/bookmarks/kdb user/sw/elektra/kdb/#0/current
You are able to use:
kdb ls +kdb/bookmarks kdb get +kdb/format
- 0: successful.
- 1: Invalid options passed.
- 2: Invalid arguments passed.
- 3: Command terminated unsuccessfully without specifying error code.
- 4: Unknown command.
- 5: KDB Error, could not read/write from/to KDB.
- 6: Reserved error code.
- 7: Unknown errors, wrong exceptions thrown.
- 8-10: Reserved error codes.
- 11-20: Command-specific error codes. See man page of specific command.