I think assigning 999 to systemd-journald conforms with both systemd's and Debian's policy, no? The systemd-journal group is a system group, and the GID is dynamically allocated (by systemd-sysusers, not adduser). See [1][2] for systemd-sysusers documentation.
It seems that fixing casper is correct, because statically/explicitly allocating a UID/GID in that range *is* in violation of both Debian's and systemd's policies.
> I think it is a bug in systemd to be bypassing the process
> specified in Debian Policy.
Note that systemd specifies its own UID/GID "spec" here: https:/ /systemd. io/UIDS- GIDS/.
I think assigning 999 to systemd-journald conforms with both systemd's and Debian's policy, no? The systemd-journal group is a system group, and the GID is dynamically allocated (by systemd-sysusers, not adduser). See [1][2] for systemd-sysusers documentation.
It seems that fixing casper is correct, because statically/ explicitly allocating a UID/GID in that range *is* in violation of both Debian's and systemd's policies.
[1] https:/ /www.freedeskto p.org/software/ systemd/ man/systemd- sysusers. html /www.freedeskto p.org/software/ systemd/ man/sysusers. d.html
[2] https:/