db

Berkeley DB is a family of embedded key-value database libraries providing scalable high-performance data management services to applications. See documentation

Maintainers

• The Core Planners: chef-core-planners@chef.io

Type of Package

Binary package

Use as Dependency

Binary packages can be set as runtime or build time dependencies. See Defining your dependencies for more information.

To add core/db as a dependency, you can add one of the following to your plan file.

Buildtime Dependency

pkg_build_deps=(core/db)

Runtime dependency

pkg_deps=(core/db)

Use as Tool

Installation

To install this plan, you should run the following commands to first install, and then link the binaries this plan creates.

hab pkg install core/db --binlink

will add the following binaries to the PATH:

• /bin/db_archive
• /bin/db_checkpoint
• /bin/db_deadlock
• /bin/db_dump
• /bin/db_hotbackup
• /bin/db_load
• /bin/db_log_verify
• /bin/db_printlog
• /bin/db_recover
• /bin/db_replicate
• /bin/db_stat
• /bin/db_tuner
• /bin/db_upgrade
• /bin/db_verify

For example:

$ hab pkg install core/db --binlink
» Installing core/db
☁ Determining latest version of core/db in the 'stable' channel
→ Using core/db/5.3.28/20200305234355
★ Install of core/db/5.3.28/20200305234355 complete with 0 new packages installed.
» Binlinking db_checkpoint from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_checkpoint from core/db/5.3.28/20200305234355 to /bin/db_checkpoint
» Binlinking db_verify from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_verify from core/db/5.3.28/20200305234355 to /bin/db_verify
» Binlinking db_load from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_load from core/db/5.3.28/20200305234355 to /bin/db_load
» Binlinking db_tuner from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_tuner from core/db/5.3.28/20200305234355 to /bin/db_tuner
» Binlinking db_upgrade from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_upgrade from core/db/5.3.28/20200305234355 to /bin/db_upgrade
» Binlinking db_archive from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_archive from core/db/5.3.28/20200305234355 to /bin/db_archive
» Binlinking db_log_verify from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_log_verify from core/db/5.3.28/20200305234355 to /bin/db_log_verify
» Binlinking db_deadlock from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_deadlock from core/db/5.3.28/20200305234355 to /bin/db_deadlock
» Binlinking db_stat from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_stat from core/db/5.3.28/20200305234355 to /bin/db_stat
» Binlinking db_printlog from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_printlog from core/db/5.3.28/20200305234355 to /bin/db_printlog
» Binlinking db_replicate from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_replicate from core/db/5.3.28/20200305234355 to /bin/db_replicate
» Binlinking db_dump from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_dump from core/db/5.3.28/20200305234355 to /bin/db_dump
» Binlinking db_hotbackup from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_hotbackup from core/db/5.3.28/20200305234355 to /bin/db_hotbackup
» Binlinking db_recover from core/db/5.3.28/20200305234355 into /bin
★ Binlinked db_recover from core/db/5.3.28/20200305234355 to /bin/db_recover

Using an example binary

You can now use the binary as normal. For example:

/bin/db_dump --help or db_dump --help

$ db_dump --help
db_dump: invalid option -- '-'
usage: db_dump [-klNprRV]
        [-d ahr] [-f output] [-h home] [-P password] [-s database] db_file
usage: db_dump [-kNpV] [-d ahr] [-f output] [-h home] -m database