No it's too late
Le mar. 27 juil. 2021 à 19:45, Thomas Uhle <
thomas.u...@mailbox.tu-dresden.de> a écrit :
> Dear maintainers,
>
> given that the current version in bullseye is still configured with
> "User=nobody" which causes this syslog message, I would like to ask if
> there is something
Dear maintainers,
given that the current version in bullseye is still configured with
"User=nobody" which causes this syslog message, I would like to ask if
there is something going to happen yet before bullseye release.
Thank you in advance!
Thomas Uhle
This should be the commit that introduced the warning:
https://github.com/systemd/systemd/commit/bed0b7dfc0070e920d00c89d9a4fd4db8d974cf0
Based on reading it, setting `DynamicUser=yes` seems to be what systemd wants
you to do.
Official documentation for `DynamicUser`:
On Sun, 20 Dec 2020 22:27:20 +0100 Alexandre Detiste
wrote:
> Hi,
>
> I don't know how to properly fix this.
> Using "root:root" seems worse.
>
> A P.R. against upstream repo is welcomed.
>
> Alexandre
>
> Le lun. 31 août 2020 à 16:54, Martin-Éric Racine
> a écrit :
> >
> > Package:
Hi,
I don't know how to properly fix this.
Using "root:root" seems worse.
A P.R. against upstream repo is welcomed.
Alexandre
Le lun. 31 août 2020 à 16:54, Martin-Éric Racine
a écrit :
>
> Package: systemd-cron
> Version: 1.5.14-2
> Severity: important
>
> Since a recent upgrade, systemd
Package: systemd-cron
Version: 1.5.14-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since a recent upgrade, systemd complains loudly via dmesg:
[ 45.787544] systemd[1]: /lib/systemd/system/cron-failure@.service:11:
Special user nobody configured, this is not safe!
[
6 matches
Mail list logo
