--On 29. Mai 2015 09:26:19 -0400 Alan DeKok <aland@deployingradius.com> wrote:
With strace I was able to see that the chown tries to set the user to UID 0, i.e. root:
Because you don't have "user = radiusd" in radiusd.conf. This is documented in radiusd.conf.
The server assumes it starts as "root". If you don't have "user = radiusd", it tries to chown() the log files to "root".
But I do: # The server will also try to use "initgroups" to read # /etc/groups. It will join all groups where "user" is a # member. This can allow for some finer-grained access # controls. # user = radiusd group = radiusd Also: # service radiusd start radiusd starten: [ OK ] [root@radius1-neu ~]# ps auxww|grep radiusd radiusd 22734 0.5 0.4 301320 8460 ? Ssl 15:32 0:00 /usr/sbin/radiusd -d /etc/raddb So the switching works when the process is started by root ... Sebastian Hagedorn -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.