Hi Guys I think the following behaviour is a bug. When radiusd is configured to run as user "radiusd" the first time it starts up, if there is no radius.log file it creates it as user root, then promptly fails because it cannot write to it as user "radiusd". # ls -l /var/log/radius total 0 drwx------ 2 radiusd radiusd 48 2006-09-02 14:34 radacct -rw-r--r-- 1 radiusd radiusd 0 2006-09-02 14:34 radutmp # rcradiusd start Starting RADIUS daemon radiusd: Couldn't open /var/log/radius/radius.log for logging: Permission denied (rlm_exec: wait=yes but no output defined. Did you mean output=none?) done # ls -l /var/log/radius total 4 drwx------ 2 radiusd radiusd 48 2006-09-02 14:34 radacct -rw-r--r-- 1 root root 208 2006-09-04 14:06 radius.log -rw-r--r-- 1 radiusd radiusd 0 2006-09-02 14:34 radutmp -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Peter Nixon <listuser@peternixon.net> wrote:
When radiusd is configured to run as user "radiusd" the first time it starts up, if there is no radius.log file it creates it as user root, then promptly fails because it cannot write to it as user "radiusd".
Ok. That happened before and I fixed it... looks like recent re-arrangements of the code broke it again. I'll take a look. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Alan DeKok -
Peter Nixon