4 Commits

Author	SHA1	Message	Date
Girish Ramakrishnan	a737d2675e	Fix logrotation rules ... * explicitly specify the dirs that are getting rotated * app log rules are now moved to logrotate.ejs * we keep task logs for a week Some testing notes: * touch -d "10 days ago" foo * logrotate /etc/logrotate.conf -v to test rotation. there is a state file created in /var/lib/logrotate/status. If we have a 'daily' rule, it will get processed only after a log line in status exists and it's atleast 1 day old timestamp. https://github.com/logrotate/logrotate/blob/master/logrotate.c is quite readable	2019-07-30 15:37:15 -07:00
Johannes Zellner	67a2ba957e	Use maxsize logrotate rule instead of size ... The current ruleset means rotate the file daily unless the file grows larger than 1Mb earlier, then rotate once the file reaches that size. https://serverfault.com/questions/474941/how-to-rotate-log-based-on-an-interval-unless-log-exceeds-a-certain-size	2017-08-16 19:10:49 +02:00
Girish Ramakrishnan	335631ac28	Look for log files in first level and third level as well	2017-08-11 16:24:56 -07:00
Johannes Zellner	2f51088e67	Add logrotate support for *.log files in /run mounts of apps ... logrotate config files may contain arbitrary commands which are exectued as root, thus the config files have to be owned by root. This is the reason we need the sudo scripts :-/ To test the generated scripts, just run: $ logrotate /etc/logrotate.conf -v Fixes #396	2017-08-12 00:04:00 +02:00