Comment 9 for bug 1187742

The symlinks in the /etc/rc?.d directories are still in place after the upstart job for FreeRADIUS was added via this bug. Is this correct or there is nothing that prevents both the init.d script and the upstart job from attempting to start the job?

Also, the upstart job seems to be tracking incorrectly the freeradius process as "reload freeradius" does not work. I notice that the upstart job does not run the FreeRADIUS executable as a daemon (-f specified) so a PID file is not written to /var/run/freeradius. The init.d script does run the server as a daemon, which is probably more correct.

Should separate bugs be filed for these two issues?

As a workaround I have disabled the upstart job and fallen back to the init.d script which does a fine job tracking the process and supporting reloads and restarts.