Hide Forgot
2. What is the nature and description of the request? rsyslog includes /var/log/boot.log in the /etc/logrotate.d/syslog file. Since the boot.log file is only written to during boot up, it doesn't need to be rotated on a schedule. 3. Why does the customer need this? (List the business requirements here) Currently, the rotation is causing a new boot.log file to get created with zero length while the old one gets a date appended to it. Eventually, when enough rotations occur, the boot.log data gets lost. 4. How would the customer like to achieve this? (List the functional requirements here) Customer is requesting to change the default behaviour so syslog will not include boot.log in logrotate.d file. 5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Test in lab environment. 6. Is there already an existing RFE upstream or in Red Hat bugzilla? No. 7. How quickly does this need resolved? (desired target release) RHEL 6.2 is the desired release. 8. Does this request meet the RHEL Inclusion criteria (please review) Yes. 9. List the affected packages rsyslog
Present in Fedora 15 also. After the boot,/var/log/boot.log is empty. The log of the boot are in var/log/boot.log-<today> rpm -qf /etc/logrotate.d/syslog rsyslog-5.7.9-3.fc15.i686
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1673.html
(In reply to comment #0) > > 9. List the affected packages > > rsyslog And syslog-ng from EPEL (as all syslog daemons packages in RedHat/Fedora must ship the same logrotate file to avoid file conflicts). File conflicts caused by this update in #767761. /jpo