I followed this link to change log-rotate configuration for RHEL 6

After I made the change to config file, what should I do to let this take effect?


logrotate uses crontab to work. It's scheduled work, not a daemon, so no need to reload its configuration.
When the crontab executes logrotate, it will use your new config file automatically.
If you need to test your config you can also execute logrotate on your own with the command:

logrotate /etc/logrotate.d/your-logrotate-config

Or as mentioned in comments, identify the logrotate line in the output of the command crontab -l and execute the command line refer to slm's answer to have a precise cron.daily explanation

  • 1
    Just to add to your answer, the cron entry for logrotate is scheduled to run once a day. – mkc Feb 20 '14 at 17:12
  • @Ketan, so, how can i make it affect right away? thanks – BufBills Feb 20 '14 at 17:17
  • Not sure. One possibility is to find the corresponding entry from crontab via crontab -l and execute it. – mkc Feb 20 '14 at 17:27
  • 2
    If you want it to take effect immediately run the cron afterwords. – slm Feb 20 '14 at 17:29
  • 2
    logrotate has a -d option for testing (or "debugging"), I'd recommend running it at least once with that. – FrustratedWithFormsDesigner Feb 23 '17 at 16:52

Most of the logrotate setups I've seen on various distros runs out of the /etc/cron.daily. There's a shell script there aptly named logrotate.


$ ls -l /etc/cron.daily/logrotate 
-rwxr-xr-x 1 root root 180 May 18  2011 /etc/cron.daily/logrotate

Manual run

If you want to make it run manually simply run the script as root:

$ sudo /etc/cron.daily/logrotate

If you take a look at a script that's typically there, it shows you how you can also run logrotate manually, by simply running logrotate + the path to its configuration file.


/usr/sbin/logrotate /etc/logrotate.conf
if [ $EXITVALUE != 0 ]; then
    /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]"
exit 0

It should be automatic via cron. You can force it to test your changes.

For global logrotate:

sudo logrotate -v -f /etc/logrotate.conf

For a single conf file:

sudo logrotate -v -f /etc/logrotate.d/someapp.conf
  • 11
    -f for force rotation, there is also -d for debug, which is also Dry run, it will print everything it would have done but not actually do it. – ThorSummoner Feb 22 '16 at 23:37

On my CentOS 6.5 machine for setting up logrotatefor nginx I had to do this:

logrotate /etc/logrotate.d/nginx

And then I checked if logrotate taking care of my new nginx config like this:

cat /var/lib/logrotate.status

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.