Comment # 8 on bug 906682 from Bob Goddard

I am still getting a small problem. Trying to start it, it needs run/radius to
exist to write the PID file which does not get created. Manually creating it
and attempting to start it does work.

Relevant output...

eth7:/etc # systemctl start radiusd.service 
Job for radiusd.service failed. See "systemctl status radiusd.service" and
"journalctl -xn" for details.
eth7:/etc # systemctl status radiusd.service
radiusd.service - FreeRADIUS high performance RADIUS server.
   Loaded: loaded (/usr/lib/systemd/system/radiusd.service; disabled)
   Active: failed (Result: exit-code) since Tue 2014-12-02 21:46:49 GMT; 5s ago
  Process: 32621 ExecStart=/usr/sbin/radiusd -d /etc/raddb (code=exited,
status=1/FAILURE)
  Process: 32619 ExecStartPre=/usr/sbin/radiusd -C (code=exited,
status=0/SUCCESS)
  Process: 32616 ExecStartPre=/bin/chown -R radiusd.radiusd /run/radiusd
(code=exited, status=1/FAILURE)

Dec 02 21:46:48 eth7 chown[32616]: /bin/chown: cannot access ���/run/radiusd���: No
such file or directory


eth7:/etc # mkdir /run/radiusd
eth7:/etc # systemctl stop radiusd.service
eth7:/etc # systemctl start radiusd.service 
eth7:/etc # netstat -anp | grep radi
udp        0      0 0.0.0.0:50486           0.0.0.0:*                          
32652/radiusd       
udp        0      0 127.0.0.1:18120         0.0.0.0:*                          
32652/radiusd       
udp        0      0 0.0.0.0:1812            0.0.0.0:*                          
32652/radiusd       
udp        0      0 0.0.0.0:1813            0.0.0.0:*                          
32652/radiusd