Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18520 - [syslog-ng] duplicate entry for crond.log in /etc/logrotate.d/syslog-ng cause error
Attached to Project:
Arch Linux
Opened by solsTiCe (zebul666) - Monday, 01 March 2010, 23:40 GMT
Last edited by Paul Mattal (paul) - Tuesday, 02 March 2010, 11:55 GMT
Opened by solsTiCe (zebul666) - Monday, 01 March 2010, 23:40 GMT
Last edited by Paul Mattal (paul) - Tuesday, 02 March 2010, 11:55 GMT
|
Detailssince i upgrade to syslog-ng-3.0.4-3, i got this error in the daily mail from cron (fcron here)
error: syslog-ng:1 duplicate log entry for /var/log/crond.log error: found error in /var/log/messages.log /var/log/auth.log /var/log/mail.log /var/log/kernel.log /var/log/errors.log /var/log/daemon.log /var/log/user.log /var/log/iptables.log /var/log/everything.log /var/log/syslog.log /var/log/acpid.log /var/log/crond.log /var/log/lpr.log /var/log/uucp.log /var/log/news.log /var/log/ppp.log /var/log/debug.log , skipping it seems there is an entry for crond.log in /etc/logrotate.d/syslog-ng whereas there is no need to because fcron provide already an /etc/logrotate.d/fcron with an crond.log entry. please remove /var/log/crond.log from /etc/logrotate.d/syslog-ng. If dcron does not provide anymore a logrotate file then create one for it instead of fixing this in logrotate and breaking other package ! please |
This task depends upon
Closed by Paul Mattal (paul)
Tuesday, 02 March 2010, 11:55 GMT
Reason for closing: Not a bug
Additional comments about closing: The /var/log/crond.log is a syslog log file, and thus needs to be managed in coordination with syslog-ng.
Tuesday, 02 March 2010, 11:55 GMT
Reason for closing: Not a bug
Additional comments about closing: The /var/log/crond.log is a syslog log file, and thus needs to be managed in coordination with syslog-ng.
like djgera said, i believe fcron should be adjusted
Who maintains fcron? I see it in unsupported but not elsewhere.
The dcron package I maintain no longer supplies a /etc/logrotate.d/crond, and that was coordinated with adding it to syslog-ng.
I'm not sure there's anything for us to do here, but I'll leave this open for a while in case others have differing opinions.
I don't understand why you're against that although it is pretty natural that dcron have its own logrotate file.
what pushed the change ?
may i ask where this have been discussed ?
Now it simply writes to syslog, which is in turn responsible for managing the log files.