Description of problem: The "olddir" directive appears to be broken. Specifically, the olddir option now seems to be interpreted relative to the directory which contains the logfile being processed. (The previous behavior was that olddir specified an absolute directory.) If this is an intentional change, then please update the documentation (i.e., the man page) to reflect the change. Version-Release number of selected component (if applicable): logwatch-4.3.1-1 How reproducible: Replace the contents of /etc/logrotate.d/rpm with this: /var/log/rpmpkgs { daily notifempty missingok rotate 7 olddir /var/log/OLD nocompress sharedscripts } Then run: /usr/sbin/logrotate --debug=100 /etc/logrotate.conf Actual results: error: rpm:9 error verifying olddir path /var/log//var/log/OLD: No such file or directory Expected results: Logrotate puts the rotated log files in /var/log/OLD.
What logrotate version are you running (logrotate, not logwatch)?
Argh... I apologize for my inability to differentiate LOGWATCH from LOGROTATE. (This isn't the first time...) $ rpm -qa | grep -i ^log | sort logrotate-3.6.6-1 logwatch-4.3.1-1
I grabbed logrotate-3.6.8-1 from Rawhide, and this bug is fixed; the olddir directive is correctly interpreted as an absolute path (the same as previous versions). Danke; I'm closing this report.