On Monday 12 August 2019 23:59:39 Teemu Likonen wrote: > phi...@treads.nz [2019-08-13T09:30:34+12] wrote: > > I just updated from Debian 8 to 9 and I'm getting the following > > error. I'm guessing it's something to do with permissions? > > > > Something to do with the create 640 root adm? > > > > /etc/cron.daily/logrotate: > > error: unable to open /home/philip/logs/access.log.1 for compression > > error: unable to open /home/philip/logs/error.log.1 for compression > > run-parts: /etc/cron.daily/logrotate exited with return code 1 > > It could be because of /home not being writable for logrotate service. > See Sven Joachim's message in 2019-07-21: > > https://lists.debian.org/debian-user/2019/07/msg01102.html
Its good that we can fix it, BUT IF you are going to restrict where we keep logfiles like this then FIX the /var/log perms so that fetchmail, procmail, spamassassin, clamav and its ilk, running as the user can access /var/log to keep its logs. Debian's legendary paranoia about who can write a log in /var/log has long since forced most of us that want that log, into moving it to /home/username/log and reprogramming logrotate to maintain it there years ago. Now you want to prevent logrotate from just doing its job? Does your paranoia not have any limits to how difficult you are making the users job? So just where in tunket _are_ we supposed to be able to keep our logs then? A place that Just Works would sure be appreciated. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
