> If I run logrotate after that, I get:
> truncated catalina.out syslog:adm 0640
How are you running logrotate? Because the problem was that it could not be truncated by rsyslog running as `tomcat` user.
Anyway, I checked your branch and your fix looks quite similar to mine. The only difference is that I had `fileOwner="syslog"` in `debian/rsyslog/tomcat9.conf` but that is inconsequential. As my setting was redundant, because the default fileowner for rsyslog is `syslog`. (in Ubuntu). So I could say, yes it works :)
That said, it is sad that there is a delta. I think this could be avoided if Debian maintainers would agree on using `root:adm` in their side and Ubuntu defaults to `syslog:adm`. As the default fileOwner is `root` for Debian and it is for Ubuntu in rsyslog. The logrotate also defaults to `root` in Debian and `syslog` in Ubuntu. But maybe it is too difficult to co-operate in this level. I do not know...
> If I run logrotate after that, I get:
> truncated catalina.out syslog:adm 0640
How are you running logrotate? Because the problem was that it could not be truncated by rsyslog running as `tomcat` user.
Anyway, I checked your branch and your fix looks quite similar to mine. The only difference is that I had `fileOwner= "syslog" ` in `debian/ rsyslog/ tomcat9. conf` but that is inconsequential. As my setting was redundant, because the default fileowner for rsyslog is `syslog`. (in Ubuntu). So I could say, yes it works :)
That said, it is sad that there is a delta. I think this could be avoided if Debian maintainers would agree on using `root:adm` in their side and Ubuntu defaults to `syslog:adm`. As the default fileOwner is `root` for Debian and it is for Ubuntu in rsyslog. The logrotate also defaults to `root` in Debian and `syslog` in Ubuntu. But maybe it is too difficult to co-operate in this level. I do not know...