Bug#1141328: jetty9: LogsDirectory= changes /var/log/jetty9 group from adm to jetty

[ofrytest at gmail.com]

I performed an additional runtime verification of this issue using the
current 9.4.58-2 packaging.

Although my test machine is running Ubuntu 26.04, I temporarily upgraded
only the Jetty packages (`jetty9`, `libjetty9-java`, and
`libjetty9-extra-java`) to version **9.4.58-2**, which uses the same
packaging as the current Debian unstable/testing package.

The result is exactly the same as reported originally.

After reboot:

```
drwxr-x--- 2 jetty jetty ... /var/log/jetty9
```

The installed service configuration confirms that the service is running
with:

```
LogsDirectory=jetty9
User=jetty
Group=jetty
```

and rsyslog reports:

```
file '/var/log/jetty9/jetty-console.log': open error: Permission denied
```

I also verified that the installed tmpfiles configuration is:

```
d /var/log/jetty9 0750 jetty adm
Z /var/log/jetty9 - jetty adm
```

Therefore, even after the migration from maintainer-script ownership
management to `systemd-tmpfiles`, the issue remains unchanged.

The observed runtime behavior matches the packaging:

* `systemd` creates and/or reassigns `/var/log/jetty9` to `jetty:jetty`
because of `LogsDirectory=jetty9`;
* `rsyslog` runs as the `syslog` user and therefore cannot create
`/var/log/jetty9/jetty-console.log`.

This confirms that the problem is still reproducible with the current
9.4.58-2 packaging.

On Fri, 3 Jul 2026 06:12:21 +0300 <ofrytest at gmail.com> wrote: 
> Package: jetty9 
> 
> Version: 9.4.58-2 
> 
> Severity: normal 
> 
>  
> 
> Subject: jetty9: LogsDirectory= changes /var/log/jetty9 group from adm to 
> jetty 
> 
>  
> 
> The package currently uses two conflicting mechanisms to manage the 
> ownership of the log directory. 
> 
>  
> 
> The tmpfiles configuration installs the directory as: 
> 
>  
> 
> ``` 
> 
> d /var/log/jetty9 0750 jetty adm 
> 
> Z /var/log/jetty9 - jetty adm 
> 
> ``` 
> 
>  
> 
> which clearly specifies that the directory group should be "adm". 
> 
>  
> 
> However, the systemd service contains: 
> 
>  
> 
> ``` 
> 
> User=jetty 
> 
> Group=jetty 
> 
> LogsDirectory=jetty9 
> 
> ``` 
> 
>  
> 
> According to the systemd.exec(5) documentation, LogsDirectory= ensures
that 
> the innermost directory is owned by the User= and Group= configured for
the 
> service. As a result, when the service starts, systemd changes the
ownership 
> of: 
> 
>  
> 
> ```