db_load man page on OSF1

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
OSF1 logo
[printable version]

db_load(8)							    db_load(8)

NAME
       db_load - Loads standard input to a database files (Enhanced Security)

SYNOPSIS
       /usr/tcb/bin/db_load  [-nT]  [-c	 name=value]  [-f  file] [-h home] [-t
       btree | hash | recno] db_file

OPTIONS
       Specify configuration options for the  DB_INFO  structure  provided  to
       db_open	ignoring  any value they may have been based on the input. The
       command-line format is name=value.

	      The following keywords are supported: The minimum number of keys
	      per  page.   The	byte order for integers in the stored database
	      metadata.	 The size of pages used for  nodes  in	the  tree,  in
	      bytes.   The  value  of the DB_DUP flag.	The density within the
	      hash table.  The size of the hash table.	 Specify  fixed-length
	      records  of  the	specified  length.   Specify  the fixed-length
	      record pad character.  The value of  the	DB_RECNUM  flag.   The
	      value  of the DB_RENUMBER flag. The parenthetical listing speci‐
	      fies how the value part of the name=value pair  is  interpreted.
	      Items  listed  as	 (boolean)  expect  value  to  be 1 (set) or 0
	      (unset). Items listed as (number) convert	 value	to  a  number.
	      Items  listed  as (string) use the characters of value directly.
	      Read from the specified input file, instead of from the standard
	      input.   Specify	a home directory for the database. The correct
	      directory for enhanced security is /var/tcb/files.  Do not over‐
	      write existing keys in the database when loading into an already
	      existing database. If a key/data pair cannot be loaded into  the
	      database	for this reason, a warning message is displayed on the
	      standard error output and the key/data pair are skipped.	The -T
	      option  allows  non-Berkeley DB applications to easily load text
	      files into databases.

	      If the database to be created is of  type	 btree	or  hash,  the
	      input  must be paired lines of text, where the first line of the
	      pair is the key item, and the second line of  the	 pair  is  its
	      corresponding  data  item.  If  the database to be created is of
	      type recno, the input must be lines of text, where each line  is
	      a new data item for the database.

	      A simple escape mechanism, where newline and backslash (\) char‐
	      acters are special, is applied to the text input. Newline	 char‐
	      acters  are  interpreted as record separators. Backslash charac‐
	      ters in the text will be interpreted in one of two ways: If  the
	      backslash	 character  precedes  another backslash character, the
	      pair will be interpreted as a literal backslash.	If  the	 back‐
	      slash character precedes any other character, the two characters
	      following the backslash will be interpreted as hexadecimal spec‐
	      ification of a single character, that is, \0a is a newline char‐
	      acter in the ASCII character set.

	      For this reason, any backslash or newline characters that	 natu‐
	      rally occur in the text input must be escaped to avoid misinter‐
	      pretation by db_load.

	      If the -T option is specified, the underlying access method type
	      must be specified using the -t option.  Specifies the underlying
	      access method. If no -t option is specified, the	database  will
	      be  loaded  into a database of the same type as was dumped, that
	      is, a hash database is created if a hash database was dumped.

	      The btree and hash databases may be converted from  one  to  the
	      other.  The  recno  databases  may not be converted to any other
	      database type or from any other database type.

DESCRIPTION
       A customized version of the Berkeley Database (Berkeley DB) is embedded
       in  the	operating  system to provide high-performance database support
       for critical security files. The DB includes full transactional support
       and  database  recovery, using write-ahead logging and checkpointing to
       record changes.

       The db_load utility reads from the standard input and loads it into the
       db_file	database  .  The  database  db_file  is created if it does not
       already exist.

       The input to db_load must be in the  output  format  specified  by  the
       db_dump utility or as specified for the -T option.

       The  db_load utility utility attaches to one or more of the Berkeley DB
       shared memory regions. In order to avoid region corruption,  it	should
       always  be  given  the  chance  to detach and exit gracefully. To cause
       db_load to clean up after itself and exit, send it an interrupt	signal
       (SIGINT).

       The  db_load  utility  can be used to load text files into the security
       databases. It is used by Tru64 UNIX utilities and  is  not  recommended
       for  use	 by  system administration. The edauth utility provides a sup‐
       ported means of loading records correctly into the security databases.

RETURN VALUES
       The db_load utility exits 0 on success, and >0 if one or more  key/data
       pairs  were  not	 loaded	 into  the  database  because  the key already
       existed, and with >1 if an error occurs.

ENVIRONMENT VARIABLES
       If the -h option is not specified and the environment variable  DB_HOME
       is set, it is used as the path of the database home. The home directory
       for security is /var/tcb/files.

FILES
       /var/tcb/files/auth.db

       /var/tcb/files/dblogs/*

SEE ALSO
       Files: authcap(4)

       Commands: edauth(8), db_dump(8)

								    db_load(8)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server OSF1

List of man pages available for OSF1

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net