Dear Maintainer,

during freeradius migration to bookworm I get some strange effects while moving from
debug (freeradius -X) to production. Until I realized the system has both
a init.d script and a systemd service. Please rm the /etc/init.d/freeradius
script.

As I'm usig the DHCP of freeradius, I need the AmbientCapabilities, which are
prepared in the /usr/lib/systemd/system/freeradius.service file as a comment.

Namely, I use:
#Those add only the two caps to allow dhcp binding of port 67 and do broadcast to local net
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE

The /usr/share/doc/freeradius/README.Debian file contains (outdated?) references to
the sysV init script, this should be updated with best mentioning the capabilities
needed for freeradius doing dhcp.

Thanks a lot!

Greetings
  Hermann

I don't think there is consensus yet to remove init-scripts just because
we can. The init script provided also redirects normal invocations to
systemctl.

I dropped README.Debian in 3.2.6+dfsg-3 and will happily accept patches
for a small new one, possibly also mentioning other settings for
non-every-day settings like in #1003286

Bernhard