Bug#1050718: logrotate without copytruncate is nicer to aide

2023-08-29 Thread Holger Levsen
On Tue, Aug 29, 2023 at 08:10:43AM +0200, Marc Haber wrote: > On Mon, Aug 28, 2023 at 05:27:12PM +, Holger Levsen wrote: > > On Mon, Aug 28, 2023 at 04:27:36PM +0200, Marc Haber wrote: > > > Please consider applying this in Debian's munin-node package. If you > > > choose to not do this (which

Bug#1050718: logrotate without copytruncate is nicer to aide

2023-08-28 Thread Marc Haber
On Mon, Aug 28, 2023 at 05:27:12PM +, Holger Levsen wrote: > On Mon, Aug 28, 2023 at 04:27:36PM +0200, Marc Haber wrote: > > Please consider applying this in Debian's munin-node package. If you > > choose to not do this (which I would fully understand, I know that I am > > asking a lot), [...]

Bug#1050718: logrotate without copytruncate is nicer to aide

2023-08-28 Thread Holger Levsen
Hi Marc, thanks for your bug report with patch! I just have one question: On Mon, Aug 28, 2023 at 04:27:36PM +0200, Marc Haber wrote: > Please consider applying this in Debian's munin-node package. If you > choose to not do this (which I would fully understand, I know that I am > asking a lot),

Bug#1050718: logrotate without copytruncate is nicer to aide

2023-08-28 Thread Marc Haber
Package: munin-node Version: 2.0.73-1 Severity: wishlist Tags: patch Hi, munin-node's logrotate file uses the copytruncate feature to avoid having to restart munin-node after log rotation. This is probably a workaround for a shortcoming in munin-node, which was filed upstream last week as https:/