Bug#969329: systemd-cron: Special user nobody configured, this is not safe!
Malte Schröder
malte.schroeder at tnxip.de
Fri Feb 26 06:38:31 GMT 2021
On Sun, 20 Dec 2020 22:27:20 +0100 Alexandre Detiste
<alexandre.detiste at gmail.com> 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
> <martin-eric.racine at iki.fi> a écrit :
> >
> > Package: systemd-cron
> > Version: 1.5.14-2
> > Severity: important
> >
> > Since a recent upgrade, systemd complains loudly via dmesg:
> >
> > [ 45.787544] systemd[1]:
/lib/systemd/system/cron-failure at .service:11: Special user nobody
configured, this is not safe!
> > [ 45.864175] systemd[1]:
/lib/systemd/system/cron-failure at .service:11: Special user nobody
configured, this is not safe!
>
>
Hi,
I just took a look at how Arch does this. Instead of User=nobody they
use DynamicUser=yes. I changed that accordingly, I will see what happens ...
/Malte
More information about the Pkg-systemd-maintainers
mailing list