secauthmigrate(8) [osf1 man page]

secauthmigrate(8)					      System Manager's Manual						 secauthmigrate(8)

NAME

       secauthmigrate - Convert ULTRIX auth(5) authentication data to authcap(4) authentication data  (Enhanced Security)

SYNOPSIS

       /usr/sbin/secauthmigrate [options] files

       ... | /usr/sbin/secauthmigrate [options] -

DESCRIPTION

       The secauthmigrate utility reads records from the specified files or from standard input (-).  These records must be formatted according to
       the ULTRIX auth(Section 5) format.  These can be generated by getauth on ULTRIX, or (for the Hesiod/BIND  master  host)	can  be  found	in
       /var/dss/namedb/src/auth.   For	each  authentication  record found, secauthmigrate will attempt to find a matching username record for the
       given UID.  If that translation can be performed, an authcap(4) entry for the extended profile information for that user  is  created  from
       the  data  in  the input record.  If the extended profile entry already exists, then the converted entry is left in /tcb/files/auth/?/user-
       name:ULT rather than overwrite the entry in /tcb/files/auth/?/username.

       If ROOTDIR is defined, it is used instead of / as the root of the directory tree when creating the /tcb/files/auth/?/* files.

FLAGS

       -v     Indicate successful conversions on standard output.

       -U     Give a long usage message.

ERRORS

       Failed to find name for UID # xxxx -- skipped
       No BSD style (/etc/passwd or NIS data) account exists. If you need this account, create a BSD style account and run secauthmigrate again.

       Existing file for username -- conversion saved in /tcb/files/auth/?/username:ULT
       Extended profile already exists. Compare the files to determine the differences.  If the differences are not related to the  password,  use
       the  dxaccounts	program  to  update  the  existing  file.   If	the  differences  are related to the password, disable logins and edit the
       /tcb/files/auth/?/username file.

       secauthmigrate -- unrecognized option '${opt}'
       The option you provided was not recognized.  The options are -v and -U.

       Usage: secauthmigrate [options] files
	   (Try secauthmigrate -U for help.)
       The -U option provides extensive help.

FILES

       ${ROOTDIR}/tcb/files/auth/?/*

RELATED INFORMATION

       authcap(4), prpasswd(4)

       auth(Section 5) and getauth(Section 8) on ULTRIX.

       Security delim off

																 secauthmigrate(8)

db_checkpoint(8)					      System Manager's Manual						  db_checkpoint(8)

NAME

       db_checkpoint - Periodically checkpoint the security database log (Enhanced Security)

SYNOPSIS

       /usr/tcb/bin/db_checkpoint [-1v] [-h home]
	    [-k bytes] [-L file] [-p min]

FLAGS

       Checkpoint  the	log  once,  and  then  exit.   Specify	a home directory for the database.  The correct directory for enhanced security is
       /var/tcb/files.	Checkpoint the database at least as often as every kbytes of log file written.	Log the  execution  of	the  db_checkpoint
       utility to the specified file in the following format, where ### is the process ID, and the date is the time the utility starting running.

       db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995

       This file is removed if the db_checkpoint utility exits gracefully.  Checkpoint the database at least every min minutes.  Write the time of
       each checkpoint to the standard output.

       At least one of the -1, -k and -p options must be specified.

DESCRIPTION

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

       The db_checkpoint utility is a daemon process that monitors the database log and periodically checkpoints it. Since  other  database  func-
       tions  also  cause checkpoint records to be written to the log, db_checkpoint is normally used as a one-time function to guarantee a check-
       point before archiving the database.

       The db_checkpoint 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_checkpoint to clean up after itself and exit, send it an
       interrupt signal (SIGINT).

       The db_checkpoint utility does not attempt to create the Berkeley DB shared memory regions if they do not already exist.   The  application
       which creates the region should be started first, and then, once the region is created, the db_checkpoint utility should be started.

RETURN VALUES

       The db_checkpoint utility exits 0 on success, and >0 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/*

RELATED INFORMATION

       Commands: db_archive(8), db_printlog(8), db_recover(8), db_stat(8), secconfig(8) delim off

																  db_checkpoint(8)