From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: section "2.12. Configuring syslogd Event Logging" of our cluster docs do describe cluster logging. we really should not tell users to modify existing files, but rather have them use /etc/logrotate.d Yes, it will happen that syslog is restarted twice in short succession if both the cluster logs and what is defined in /etc/logrotate.d/syslog need rotating in one logrotate run, but IMHO that is acceptable. filing this against the software and not the docs as I think we really should just drop in the file when the rpm installs. Shame we have no /etc/syslog.d to drop the "logging to /var/log/cluster"-lines into. Version-Release number of selected component (if applicable): How reproducible: Always Actual Results: telling the reader to modify a file from the logrotate RPM Expected Results: telling the user to do it the clean way by dropping a file in /etc/syslog.d Additional info: [root@dl380g2-bottom logrotate.d]# cat cluster /var/log/cluster { sharedscripts postrotate /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true endscript }
Internal RFE bug #116411 entered; will be considered for future releases.
This is not getting fixed Red Hat Cluster Suite 3 at this point.