I get the following error message: warning: state file /var/lib/misc/logrotate.status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... This is fully bullshit for two reasons: 1. `ls /var/lib/misc/logrotate.status` gives: ~> ll /var/lib/misc/logrotate.status -rw-r----- 1 root root 1,2K 16. Jul 16:45 /var/lib/misc/logrotate.status So the file is neither world readable nor by any user. 2. Even if it is setup that way, it is fully choice of root to do so. He has full control over the config files of logrotate (if he has not, he would have much bigger problems!) Reproducible: Always Steps to Reproduce: 1. run logrotate 2. 3. Actual Results: It spams about a not world readable world readable file Expected Results: It would work without complaining
Please be more polite instead of talking about "bullshit". Does the warning occur more than once? At least in bug 847382, the discussion (and my experience) seemed to conclude that it was a one-off warning at most.
Well, I got it multiple times and I remember the last time that I was already pissed about the … message. I take security and messages about it very serious. It cost me many times to get to the root of such messages. If is comes out to be … (sorry, I don't know any other word than that I already used), I am really pissed. And I only take the burden to open a bug if it comes again. The system is a laptop where logrotate is not running regular.
I am afraid the steps to reproduce are too vague to take any action on this. Please provide the output of two runs of `logrotate -v ...` on a single state file.
