(First post ever so if it looks like a drunk spider has formatted it then sorry) After using our friend Google, here and I can’t remember where else I managed to achieve something using logrotate (rather than cron or some other equivalent). I have a the following in /var/log/rsync/: -rw-r–r– 1 root root 1.1M Apr … Read more
just add su root adm to the config file: /var/log/apache2/*.log { # … su root adm }
The manpage of logrotate.conf contains an important advice for the hourly option: Log files are rotated every hour. Note that usually logrotate is configured to be run by cron daily. You have to change this configuration and run logrotate hourly to be able to really rotate logs hourly. As pointed out by yellow1pl the solution … Read more
As mentioned by Zeeshan, the logrotate options size, minsize, maxsize are triggers for rotation. To better explain it. You can run logrotate as often as you like, but unless a threshold is reached such as the filesize being reached or the appropriate time passed, the logs will not be rotated. The size options do not … Read more
The key is knowing that CentOS runs the scripts in /etc/cron.{daily,weekly,monthly} from anacron… /etc/anacrontab is setting RANDOM_DELAY, which does what you might expect (it delays up to RANDOM_DELAY minutes before starting the job)… # /etc/anacrontab: configuration file for anacron # See anacron(8) and anacrontab(5) for details. SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # the maximal random delay added … Read more
I use the create directive in my /etc/logrotate.d/ files. Example: create 0664 www-data www-data
How do you know the file is not getting rotated? On a Debian 6 Linode I have, in the default configuration logrotate was only scheduled by cron to run once per day, and at a very odd time at that. If only run once per day, naturally it’ll only have one opportunity per day to … Read more
While the world is divided on whether the humble named pipe is friend or foe, it is probably the simplest solution to your problem. It does have a few drawbacks (in that you need to create the pipes ahead of time), but it eliminates the need for a cron and allows you to used the … Read more
your configuration says: rotate 2 that means log files are rotated 2 times before being removed, so logrotate only cares about 2 files. my guess is that the configuration was changed at some point, because previously more log files were kept, maybe it was something like rotate 28. these older files you have to remove … Read more
This is probably because even though you truncate the file, the process writing to the file will continue writing at whichever offset it were at last. So what’s happening is that logrotate truncates the file, size is zero, process writes to the file again, continuing at the offset it left off, and you now have … Read more