Index for Section 4

Alphabetical listing for B

Bottom of page

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
  /etc/binlog.auth
	     Location of the authorization file.

RELATED INFORMATION
  Commands: binlogd(8)

  System Administration

Index for Section 4

Alphabetical listing for B

Top of page