SASL AuthN to LDAP
Brian Candler
b.candler at pobox.com
Tue Oct 18 17:47:15 CEST 2016
On 18/10/2016 16:02, Brendan Kearney wrote:
> thanks, i figured it was going to be something along those lines.
> with systemd based OS's, you can created a directory, such as
> /etc/systemd/system/radiusd.d/ and put a .conf file in there to
> override or augment the service, but that does nothing for command line.
Ubuntu 16.04 handles it like this:
# cat /lib/systemd/system/freeradius.service
[Unit]
Description=FreeRADIUS multi-protocol policy server
After=syslog.target network.target
Documentation=man:radiusd(8) man:radiusd.conf(5)
http://wiki.freeradius.org/ http://networkradius.com/doc/
[Service]
Type=forking
PIDFile=/run/freeradius/freeradius.pid
EnvironmentFile=-/etc/default/freeradius
ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cxm -lstdout
ExecStart=/usr/sbin/freeradius $FREERADIUS_OPTIONS
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.target
... then you can set FREERADIUS_OPTIONS in /etc/default/freeradius, but
you can also set other environment variables including KRB5_*
> running radiusd -X will never pick up the systemd "helper" config.
> is there a way have that "helper" sourced when running radiusd -X?
If you're running it from the shell, then systemd (fortunately) knows
nothing about it. It's the one part of system operation that systemd
doesn't try to mess with :-)
You can always write a wrapper script which sources /etc/default/freeradius.
B.
More information about the Freeradius-Users
mailing list