How to make log-rotate change take effect
crontabto work. It's scheduled work, not a daemon, so no need to reload its configuration.
logrotate, it will use your new config file automatically.
If you need to test your config you can also execute
logrotateon your own with the command:
Or as mentioned in comments, identify therefer to slm's answer to have a precise cron.daily explanation
logrotateline in the output of the command
crontab -land execute the command line
Just to add to your answer, the cron entry for `logrotate` is scheduled to run once a day.
Not sure. One possibility is to find the corresponding entry from crontab via `crontab -l` and execute it.
`/you/config/file` can be misunderstood as a path to a particular config for some application's logs, such as `/etc/logrotate.d/foo`. This is usually wrong; only the main config should be used because others can inherit some values from the main one.
`logrotate` has a `-d` option for testing (or "debugging"), I'd recommend running it at least once with that.
A very common frustration is the new, required su directive `su root syslog`. Which brings logrotate to a halt when not added in. To top off people's frustration, when they add the directive, and then run (force) logrotate, it continues to spit out "`error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root" ...`" for 20 hrs after the config change, as if the the settings/process are cached!? If you are stuck there, chgrp on /var/log to root, run logrotate, chgrp back to syslog. It will clear up by next run