3.1.x systemd startup

[Jonathan Gazeley]

I've just built 3.1.x from git head this morning (commit 307c8a9) and 
while it works properly when executed as radiusd -X, it will not startup 
when started via systemctl on CentOS 7.


[jg4461 at radius-el7 ~]$ sudo service radiusd start
Redirecting to /bin/systemctl start  radiusd.service
Job for radiusd.service failed because the control process exited with 
error code. See "systemctl status radiusd.service" and "journalctl -xe" 
for details.

[jg4461 at radius-el7 ~]$ sudo journalctl -xe
Mar 09 11:55:58 radius-el7 systemd[1]: Starting FreeRADIUS 
multi-protocol policy server...
-- Subject: Unit radiusd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit radiusd.service has begun starting up.
Mar 09 11:55:58 radius-el7 radiusd[1195]: Usage: radiusd [options]
Mar 09 11:55:58 radius-el7 radiusd[1195]: Options:
Mar 09 11:55:58 radius-el7 radiusd[1195]: -C            Check 
configuration and exit.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -d <raddb>    Set 
configuration directory (defaults to /etc/raddb).
Mar 09 11:55:58 radius-el7 systemd[1]: radiusd.service: control process 
exited, code=exited status=1
Mar 09 11:55:58 radius-el7 radiusd[1195]: -D <dictdir>  Set main 
dictionary directory (defaults to /usr/share/freeradius).
Mar 09 11:55:58 radius-el7 radiusd[1195]: -f            Run as a 
foreground process, not a daemon.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -h            Print this help 
message.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -l <log_file> Logging output 
will be written to this file.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -m            On SIGINT or 
SIGQUIT clean up all used memory instead of just exiting.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -n <name>     Read 
raddb/name.conf instead of raddb/radiusd.conf.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -P            Always write out 
PID, even with -f.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -s            Do not spawn 
child processes to handle requests (same as -ft).
Mar 09 11:55:58 radius-el7 radiusd[1195]: -t            Disable threads.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -v            Print server 
version information.
Mar 09 11:55:58 radius-el7 radiusd[1195]: -X            Turn on full 
debugging (similar to -tfxxl stdout).
Mar 09 11:55:58 radius-el7 radiusd[1195]: -x            Turn on 
additional debugging (-xx gives more debugging).
Mar 09 11:55:58 radius-el7 systemd[1]: Failed to start FreeRADIUS 
multi-protocol policy server.
-- Subject: Unit radiusd.service has failed

The radiusd.service unit specifies to start with -m, but when I run this 
by hand...

[jg4461 at radius-el7 ~]$ sudo radiusd -m
Usage: radiusd [options]
Options:
   -C            Check configuration and exit.
   -d <raddb>    Set configuration directory (defaults to /etc/raddb).
   -D <dictdir>  Set main dictionary directory (defaults to 
/usr/share/freeradius).
   -f            Run as a foreground process, not a daemon.
   -h            Print this help message.
   -l <log_file> Logging output will be written to this file.
   -m            On SIGINT or SIGQUIT clean up all used memory instead 
of just exiting.
   -n <name>     Read raddb/name.conf instead of raddb/radiusd.conf.
   -P            Always write out PID, even with -f.
   -s            Do not spawn child processes to handle requests (same 
as -ft).
   -t            Disable threads.
   -v            Print server version information.
   -X            Turn on full debugging (similar to -tfxxl stdout).
   -x            Turn on additional debugging (-xx gives more debugging).


Has the -m option been changed or taken away? It still appears in the 
usage message and the systemd unit. I guess either -m needs to be fixed, 
or removed from the docs etc.

Thanks,
Jonathan

-- 
Jonathan Gazeley
Senior Systems Administrator
IT Services
University of Bristol