cfgmgr.auth(4) [osf1 man page]

cfgmgr.auth(4)						     Kernel Interfaces Manual						    cfgmgr.auth(4)

NAME

       cfgmgr.auth - Configuration management server authorization database

SYNOPSIS

       /etc/cfgmgr.auth

DESCRIPTION

       The  cfgmgr.auth  file lists the remote systems that are authorized to modify the local system's kernel subsystem configuration.  Using the
       sysconfig command, system administrators can maintain the kernel subsystem configuration on local and remote hosts.  To	secure	access	to
       the  kernel  subsystem configuration, the local configuration management server (cfgmgr) answers requests from remote systems only when the
       remote system is listed in the cfgmgr.auth file.

       Each entry in the file has the following form:

       host-name

       Where host-name specifies the full domain name of the remote host.  You must list each remote host on a separate line and  only	the  first
       128 characters of each line are read and processed.  Lines beginning with the pound sign (#) are comments.

       If  the cfgmgr.auth file does not exist, the configuration management server assumes no remote system administrators are allowed to config-
       ure, reconfigure, or unconfigure any kernel subsystem on the local host.

EXAMPLES

       The following shows entries in the cfgmgr.auth file on a host named buster:

       salmon.zk3.dec.com
       trout.zk3.dec.com
       bluefish.zk3.dec.com

       This cfgmgr.auth file allows system administrators on the salmon, trout, and bluefish hosts to configure, reconfigure, and unconfigure sub-
       systems on buster.

RELATED INFORMATION

       Commands: cfgmgr(8), sysconfig(8), sysconfigdb(8), kloadsrv(8)

       Files:  /etc/sysconfigtab(4)

       System Administration delim off

																    cfgmgr.auth(4)

binlog.auth(4)						     Kernel Interfaces Manual						    binlog.auth(4)

NAME

       binlog.auth -  authorization file for accepting remote binlog messages

SYNOPSIS

       # format:  Each fully qualified host name on a separate line hostname.domain_name

DESCRIPTION

       The  /etc/binlog.auth file specifies which remote hosts are allowed to forward binlog messages to the local host. For the sake of security,
       only messages coming from remote hosts listed in the local /etc/binlog.auth file will be logged by the binlogd daemon.

       Each remote host name should appear in a separate line in /etc/binlog.auth.  A line started with the # character is considered as a comment
       and is thus ignored.

       A  host	name must be a complete domain name such as trout.zk3.dec.com.	If a domain host name is given, it must either appear in the local
       /etc/hosts file or be able to be resolved by the name server.

       Note that a host name can have at most as many characters as defined by the MAXHOSTNAMELEN constant in <sys/param.h>, although each line in
       the /etc/binlog.auth file can have up to 512 characters.

       The /etc/binlog.auth file must be owned by root and has a permission of 0600.

       If  the	/etc/binlog.auth  file does not exist or it exists but is empty or has no valid remote host names in it, the system will assume no
       remote host is allowed to forward binlog messages to the local host.

       To invoke a new version of the /etc/binlog.auth file, run the following command (as the super user) to re-initialize  the  binlogd  daemon:
       kill -HUP `cat /var/run/binlogd.pid`

EXAMPLES

       The  following  example	provides  a  typical  authorization  file:  #  format:	 Each  fully  qualified  host  name  on  a  separate  line
       c3poid.rvo.dec.com r2d2id.ckt.dec.com

FILES

       Location of the authorization file.

RELATED INFORMATION

       Commands: binlogd(8)

       System Administration delim off

																    binlog.auth(4)