ldbedit(1) [suse man page]

LDBEDIT(1)							   User Commands							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 4.0 of the Samba suite.

SEE ALSO

       ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)

AUTHOR

       ldb was written by Andrew Tridgell.

       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.

Samba 3.5							    06/18/2010								LDBEDIT(1)

CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME

     crontab -- maintain crontab files for individual users (V3)

SYNOPSIS

     crontab [-u user] file
     crontab [-u user] { -l | -r | -e }

DESCRIPTION

     The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron.  Each user
     can have their own crontab, and though these are files in /var, they are not intended to be edited directly.

     If the allow file exists, then you must be listed therein in order to be allowed to use this command.  If the allow file does not exist but
     the deny file does exist, then you must not be listed in the deny file in order to use this command.  If neither of these files exists, then
     depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to
     use this command.	The format of these files is one username per line, with no leading or trailing whitespace.  Lines of other formats will
     be ignored, and so can be used for comments.

     The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.

     The following options are available:

     -u      Specify the name of the user whose crontab is to be tweaked.  If this option is not given, crontab examines ``your'' crontab, i.e.,
	     the crontab of the person executing the command.  Note that su(1) can confuse crontab and that if you are running inside of su(1) you
	     should always use the -u option for safety's sake.

     -l      Display the current crontab on standard output.

     -r      Remove the current crontab.

     -e      Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables.  The specified editor must edit
	     the file in place; any editor that unlinks the file and recreates it cannot be used.  After you exit from the editor, the modified
	     crontab will be installed automatically.

FILES

     /var/cron/allow  List of users allowed to use crontab
     /var/cron/deny   List of users prohibited from using crontab
     /var/cron/tabs   Directory for personal crontab files

DIAGNOSTICS

     A fairly informative usage message appears if you run it with a bad command line.

SEE ALSO

     crontab(5), cron(8)

STANDARDS

     The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'') with the exception that the dangerous variant of calling crontab without a file
     name in the first form of the command is not allowed by this implementation.  The pseudo-filename '-' must be specified to read from standard
     input.  The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax.

AUTHORS

     Paul Vixie <paul@vix.com>

BSD
								   May 13, 2010 							       BSD