Hi, (switching to devel) (for the benefit of those who don't have the FC16 file at hand, original is attached) ah, that looks like a good start already. Some things of interest maybe: ExecStartPre=/usr/sbin/radiusd -C ExecStart=/usr/sbin/radiusd -d /etc/raddb The config check doesn't explicitly set the config dir, while startup does. if $raddbdir != /etc/raddb, the config check will test a different configuration than what startup uses. On FC, you may simply want to set that in sync (with FR's built-in knowledge where to find raddb, maybe simply leave out the -d on ExecStart?), but for the general distribution, we could include it into the "auto" build system so that all paths are filled in with what is set during configure time. Would affect PIDFile=/var/run/radiusd/radiusd ExecStartPre=-/bin/chown -R radiusd.radiusd /var/run/radiusd ExecStartPre=/usr/sbin/radiusd -C ExecStart=/usr/sbin/radiusd -d /etc/raddb ExecReload=/usr/sbin/radiusd -C All these work on explicit paths. I'm not much into autohell, what I meant is that there should be some kind of "radiusd.service.in" which expands PIDFile=${localstatedir}/run/radiusd/radiusd ExecStartPre=-/bin/chown -R radiusd.radiusd ${localstatedir}/run/radiusd ExecStartPre=/usr/sbin/radiusd -C ExecStart=${sbindir}/radiusd ExecReload=${sbindir}/radiusd -C during "make" to the values that were found out/set during configure. Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473