Thank you Bernhard, that's fixed the issue. Is there any reason that the Bullseye version runs as a foreground process vs Buster which doesn't? Or is that a question for freeradius themselves?
Thanks On Mon, 23 Aug 2021 at 23:13, Bernhard Schmidt <be...@debian.org> wrote: > Hi, > > I haven't tested it, but I think it's expected > > On systemd systems Freeradius is started with > > ExecStart=/usr/sbin/freeradius -f $FREERADIUS_OPTIONS > > So it runs in foreground (-f). There is an option that says > > -f Run as a foreground process, not a daemon. > -P Always write out PID, even with -f. > > so I would try to add "-P" to FREERADIUS_OPTIONS /etc/default/freeradius. > > Bernhard >
