Hello Tanguy, Tanguy Ortolo [2010-04-01 15:10 +0200]: > Here, the directory /var/log/postgresql/ itself is missing, not the log > file. So the problem is not that logrotate finds no log file, but rather > that it is unable to glob the log path /var/log/postgresql/*.log. This > produces messages like: > >> /etc/cron.daily/logrotate: > >> error: error accessing /var/log/postgresql: No such file or directory > >> error: postgresql-common:1 glob failed for /var/log/postgresql/*.log
Right, I'm aware of that. I still think logcheck shouldn't complain about this with "missingok", but I'm fine to add a workaround. > * letting postgresql-common manage the log files of zero or more > postgresql servers instead of one or more, by simply creating the > /var/log/postgresql directory; This seems sensible. It could be shipped in the package, and additional I'll have to fix pg_dropcluster to not rmdir /var/log/postgresql when it's empty (i. e. when removing the last cluster). Can you confirm that logcheck is silent if the directory merely exists? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
