Distributed Systems Administration Utilities User's Guide, Linux, March 2009

source s_syslog_tcp { tcp(port(tcp_port) keep-alive(yes)
max-connections(N)); };
where N is the expected number of clients.
Next, the wizard prompts for which local logs should be consolidated:
Log files that reside on this system can be consolidated.
Would you like to consolidate this system's syslogs? (y/n) [y]:
Answering yes places this log consolidation system’s own local syslog data in the consolidated
log along with the client system's syslog data. The wizard displays a summary of all the
configuration choices made by the administrator:
Summary of Log Consolidation Configuration:
You have chosen to configure hostname as a Log
Consolidation Server.
Logs will be forwarded from the remote consolidation
clients to local port 1776 using the TCP protocol.
The consolidated logs will be stored under directory:
/clog
The following logs from the local system will be
consolidated:
Syslog
If these choices are correct, continue:
Do you want to continue? (y/n) [y]: y
The wizard displays its progress by describing which files are being modified and warns that
Ctrl/C is disabled until configuration is done. For a complete description of the modified files,
refer to “Manually Configuring Log Consolidation” (page 59).
Copying files that will be modified by the wizard to
/var/opt/dsau/root_tmp/clog. These files will be used to
restore the system to its current log consolidation
configuration, in the event of a failure.
Configuring hostname as a log consolidation server.
Creating the /etc/syslog-ng.conf.server configuration
file.
Creating a symbolic link from /etc/syslog-ng.conf to the
/etc/syslog-ng.conf.server configuration file.
Creating the syslog-ng configuration file, the log
consolidation configuration file.
Registering the log consolidation ports in the
/etc/services file.
Starting syslog-ng.
Successfully configured hostname as a log consolidation
server.
3.3.1.2 Configuring a Serviceguard Cluster as a Log Consolidation Server with clog_wizard
When running the clog_wizard (see clog_wizard(1M)) in a cluster, first make sure that all the
cluster members are up and available. The wizard needs to perform configuration operations
on each member. It only needs to be run once, from any member of the cluster. If you run the
wizard more than once, additional prompts may appear.
52 Consolidated Logging