ldbedit(1) [centos man page]
LDBEDIT(1) System Administration tools LDBEDIT(1) NAME
ldbedit - Edit LDB databases using your preferred editor SYNOPSIS
ldbedit [-?] [--usage] [-s base|one|sub] [-b basedn] [-a] [-e editor] [-H LDB-URL] [expression] [attributes...] DESCRIPTION
ldbedit is a utility that allows you to edit LDB entries (in tdb files, sqlite files or LDAP servers) using your preferred editor. ldbedit generates an LDIF file based on your query, allows you to edit the LDIF, and then merges that LDIF back into the LDB backend. OPTIONS
-?, --help Show list of available options, and a phrase describing what that option does. --usage Show list of available options. This is similar to the help option, however it does not provide any description, and is hence shorter. -H <ldb-url> LDB URL to connect to. For a tdb database, this will be of the form tdb://filename. For a LDAP connection over unix domain sockets, this will be of the form ldapi://socket. For a (potentially remote) LDAP connection over TCP, this will be of the form ldap://hostname. For an SQLite database, this will be of the form sqlite://filename. -s one|sub|base Search scope to use. One-level, subtree or base. -a, -all Edit all records. This allows you to apply the same change to a number of records at once. You probably want to combine this with an expression of the form "objectclass=*". -e editor, --editor editor Specify the editor that should be used (overrides the VISUAL and EDITOR environment variables). If this option is not used, and neither VISUAL nor EDITOR environment variables are set, then the vi editor will be used. -b basedn Specify Base Distinguished Name to use. -v, --verbose Make ldbedit more verbose about the operations that are being performed. Without this option, ldbedit will only provide a summary change line. ENVIRONMENT
LDB_URL LDB URL to connect to. This can be overridden by using the -H command-line option.) VISUAL and EDITOR Environment variables used to determine what editor to use. VISUAL takes precedence over EDITOR, and both are overridden by the -e command-line option. VERSION
This man page is correct for version 1.1 of LDB. SEE ALSO
ldb(3), ldbmodify(1), ldbdel(1), ldif(5), vi(1) AUTHOR
ldb was written by Andrew Tridgell[1]. If you wish to report a problem or make a suggestion then please see the http://ldb.samba.org/ web site for current contact and maintainer information. This manpage was written by Jelmer Vernooij and updated by Brad Hards. NOTES
1. Andrew Tridgell http://samba.org/~tridge/ LDB 1.1 06/17/2014 LDBEDIT(1)
Check Out this Related Man Page
LDB(3) [FIXME: manual] LDB(3) NAME
ldb - A light-weight database library SYNOPSIS
#include <ldb.h> DESCRIPTION
ldb is a light weight embedded database library and API. With a programming interface that is very similar to LDAP, ldb can store its data either in a tdb(3) database or in a real LDAP database. When used with the tdb backend ldb does not require any database daemon. Instead, ldb function calls are processed immediately by the ldb library, which does IO directly on the database, while allowing multiple readers/writers using operating system byte range locks. This leads to an API with very low overheads, often resulting in speeds of more than 10x what can be achieved with a more traditional LDAP architecture. In a taxonomy of databases ldb would sit half way between key/value pair databases (such as berkley db or tdb) and a full LDAP database. With a structured attribute oriented API like LDAP and good indexing capabilities, ldb can be used for quite sophisticated applications that need a light weight database, without the administrative overhead of a full LDAP installation. Included with ldb are a number of useful command line tools for manipulating a ldb database. These tools are similar in style to the equivalent ldap command line tools. In its default mode of operation with a tdb backend, ldb can also be seen as a "schema-less LDAP". By default ldb does not require a schema, which greatly reduces the complexity of getting started with ldb databases. As the complexity of you application grows you can take advantage of some of the optional schema-like attributes that ldb offers, or you can migrate to using the full LDAP api while keeping your exiting ldb code. If you are new to ldb, then I suggest starting with the manual pages for ldbsearch(1) and ldbedit(1), and experimenting with a local database. Then I suggest you look at the ldb_connect(3) and ldb_search(3) manual pages. TOOLS
o ldbsearch(1) - command line ldb search utility o ldbedit(1) - edit all or part of a ldb database using your favourite editor o ldbadd(1) - add records to a ldb database using LDIF formatted input o ldbdel(1) - delete records from a ldb database o ldbmodify(1) - modify records in a ldb database using LDIF formatted input FUNCTIONS
o ldb_connect(3) - connect to a ldb backend o ldb_search(3) - perform a database search o ldb_add(3) - add a record to the database o ldb_delete(3) - delete a record from the database o ldb_modify(3) - modify a record in the database o ldb_errstring(3) - retrieve extended error information from the last operation o ldb_ldif_write(3) - write a LDIF formatted message o ldb_ldif_write_file(3) - write a LDIF formatted message to a file o ldb_ldif_read(3) - read a LDIF formatted message o ldb_ldif_read_free(3) - free the result of a ldb_ldif_read() o ldb_ldif_read_file(3) - read a LDIF message from a file o ldb_ldif_read_string(3) - read a LDIF message from a string o ldb_msg_find_element(3) - find an element in a ldb_message o ldb_val_equal_exact(3) - compare two ldb_val structures o ldb_msg_find_val(3) - find an element by value o ldb_msg_add_empty(3) - add an empty message element to a ldb_message o ldb_msg_add(3) - add a non-empty message element to a ldb_message o ldb_msg_element_compare(3) - compare two ldb_message_element structures o ldb_msg_find_int(3) - return an integer value from a ldb_message o ldb_msg_find_uint(3) - return an unsigned integer value from a ldb_message o ldb_msg_find_double(3) - return a double value from a ldb_message o ldb_msg_find_string(3) - return a string value from a ldb_message o ldb_set_alloc(3) - set the memory allocation function to be used by ldb o ldb_set_debug(3) - set a debug handler to be used by ldb o ldb_set_debug_stderr(3) - set a debug handler for stderr output AUTHOR
ldb was written by Andrew Tridgell[1]. If you wish to report a problem or make a suggestion then please see the http://ldb.samba.org/ web site for current contact and maintainer information. ldb is released under the GNU Lesser General Public License version 2 or later. Please see the file COPYING for license details. NOTES
1. Andrew Tridgell http://samba.org/~tridge/ [FIXME: source] 04/19/2012 LDB(3)