On Wednesday 24 July 2019 21:04:13 Tan Shao Yi wrote:
> Hi Sven,
>
> Thank you for the explanation.
>
> I just wanted to add that when doing "systemctl edit
> logrotate.service", we also need to include the "[Service]" header
> before specifying ReadWritePaths.
>
> Thank you.
>
> Regards,
> Tan Sh
Hi Sven,
Thank you for the explanation.
I just wanted to add that when doing "systemctl edit logrotate.service", we
also need to include the "[Service]" header before specifying ReadWritePaths.
Thank you.
Regards,
Tan Shao Yi
On 21/7/19, 5:55 PM, "Sven Joachim" wrote:
On 2019-07-21 02:4
Sven Joachim, on 2019-07-21:
> On 2019-07-21 02:42 +, Tan Shao Yi wrote:
> > May I know if something has changed recently to cause this?
>
> It is the ProtectSystem=full directive in logrotate.service which causes
> /usr to be mounted read-only for logrotate. See the SANDBOXING section
> in sy
On 2019-07-21 02:42 +, Tan Shao Yi wrote:
> I upgraded to Debian 10 recently and it looks like logrotate is not
> working on files outside the /var directory:
This is correct.
> For example,
>
> Jul 21 00:00:01 server-name logrotate[8874]: error: error renaming
> /usr/local/apache/logs/https
Good day Tan Shao Yi,
Tan Shao Yi, on 2019-07-21:
> For example,
>
> Jul 21 00:00:01 server-name logrotate[8874]: error: error renaming
> /usr/local/apache/logs/https-error_log.12.gz to
> /usr/local/apache/logs/https-error_log.13.gz: Read-only file system
Here I would have suggested to have a l
5 matches
Mail list logo
