Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3214
mail.debug @<log consolidation server>
*.info;mail.none @<log consolidation server>
where <log consolidation server> is the fully qualified domain
name of the local cluster member. The name must be fully qualified or
syslogd will not forward messages properly.
If you have customized syslog.conf, make sure to add the
forwarding lines for your customizations as well.
c. Since /etc/rc.config.d/syslogd is generic, it can be distributed
cluster-wide using ccp, as follows:
# cpp /etc/rc.config.d/syslogd /etc/rc.config.d/
d. The /etc/syslog.conf is specific to each member and the edits
described above must be performed on each cluster member.
e. Making the above changes on each cluster member, syslogd must be
restarted for these changes to take affect. Use cexec to do this on all
members of the cluster:
# cexec “/sbin/init.d/syslogd stop;/sbin/init.d/syslogd start”
Step 2. To configure syslog-ng, start with the same syslog-ng.conf templates
used by the clog_wizard. On one cluster member, copy
/opt/dsau/share/clog/templates/syslog-ng.conf.server.templa
te to /etc/syslog-ng.conf.server. Then copy an
/opt/dsau/share/clog/templates/syslog-ng.conf.client.templa
te to /etc/syslog-ng.conf.client. Both files have tokens named
<%token-name%> that are replaced by the wizard based on the
administrator’s answers to the wizard’s questions.
Manually replace the tokens in /etc/syslog-ng.conf.server as
follows:
a. When using the TCP protocol and configuring the consolidation
server to consolidate its own syslogs, replace the
<%UDP_LOOPBACK_SOURCE%> token with:
source s_syslog_udp { udp(port(514)); };
Replace the <%UDP_LOOPBACK_LOG%> token with:
log { source(s_syslog_udp); destination(d_syslog_tcp); };