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#17178 - [shorewall] logrotate
Attached to Project:
Community Packages
Opened by orbisvicis (orbisvicis) - Tuesday, 17 November 2009, 17:47 GMT
Last edited by Dan Griffiths (Ghost1227) - Saturday, 09 January 2010, 01:32 GMT
Opened by orbisvicis (orbisvicis) - Tuesday, 17 November 2009, 17:47 GMT
Last edited by Dan Griffiths (Ghost1227) - Saturday, 09 January 2010, 01:32 GMT
|
DetailsDescription:
. The recent update to shorewall (IPv4 version) adds /var/log/shorewall-init.log and bumps the log verbosity up to two (STARTUP_LOG and LOG_VERBOSITY). . Shorewall also continues to log to /var/log/messages.log, which is already rotated by syslog-ng. . Shouldn't the new log file be managed by logrotate? Additional info: shorewall 4.4.3-1 Other Stuff: The shorewall.conf and shorewall6.conf files do not seem to be very consistent between releases (besides adding new features) and in comparison to each other. Perhaps wait a point release to see if the shorewall-init.log is kept? |
This task depends upon
Closed by Dan Griffiths (Ghost1227)
Saturday, 09 January 2010, 01:32 GMT
Reason for closing: Not a bug
Additional comments about closing: Two versions later and the log is still there. As this package is currently unmaintained (and has been for some time). If you would like to implement the feature you have requested, would you be willing to maintain the package? If so, please contact me and I will have it moved to AUR so that you can take over its maintenance.
Saturday, 09 January 2010, 01:32 GMT
Reason for closing: Not a bug
Additional comments about closing: Two versions later and the log is still there. As this package is currently unmaintained (and has been for some time). If you would like to implement the feature you have requested, would you be willing to maintain the package? If so, please contact me and I will have it moved to AUR so that you can take over its maintenance.