Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

binlog.auth(4) [osf1 man page]

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)

Check Out this Related Man Page

SAVE_BINARY_LOGS(1p)					User Contributed Perl Documentation				      SAVE_BINARY_LOGS(1p)

NAME
save_binary_logs - Concatenating binary or relay logs from the specified file/position to the end of the log. This command is automatically executed from MHA Manager on failover, and manual execution should not be needed normally. SYNOPSIS
# Test $ save_binary_logs --command=test --binlog_dir=/var/lib/mysql --start_file=mysqld-bin.000002 # Saving binary logs $ save_binary_logs --command=save --binlog_dir=/var/lib/mysql --start_file=mysqld-bin.000002 --start_pos=312 --output_file=/var/tmp/aggregate.binlog # Saving relay logs $ save_binary_logs --command=save --start_file=mysqld-relay-bin.000002 --start_pos=312 --relay_log_info=/var/lib/mysql/relay-log.info --output_file=/var/tmp/aggregate.binlog save_binary_logs concatenates binary or relay logs from the specified log file/position to the end of the log. This tool is intended to be invoked from the master failover script(MHA Manager), and manual execution is normally not needed. DESCRIPTION
Suppose that master is crashed and the latest slave server has received binary logs up to mysqld-bin.000002:312. It is likely that master has more binary logs. If it is not sent to the slave, slaves will lose all binlogs from mysqld-bin.000002:312. The purpose of the save_binary_logs is to save binary logs that are not replicated to slaves. If master is reachable through SSH and binary logs are readable, saving binary logs is possible. Here is an example: $ save_binary_logs --command=save --start_file=mysqld-bin.000002 --start_pos=312 --output_file=/var/tmp/aggregate.binlog Then all binary logs starting from mysqld-bin.000002:312 are concatenated and stored into /var/tmp/aggregate.binlog. If you have binary logs up to mysqld-bin.000004, the following mysqlbinlog outputs are written. mysqld-bin.000002:Format Description Event(FDE), plus from 312 to the tail mysqld-bin.000003:from 0 to the tail, excluding FDE mysqld-bin.000004:from 0 to the tail, excluding FDE perl v5.14.2 2012-01-08 SAVE_BINARY_LOGS(1p)
Man Page