John Dennis wrote:
FWIW, in our RPM's we force the creation of the radius.log file with
ownership radiusd:radiusd at installation time before the server even runs.
This should also be in the /etc/init.d/radiusd script.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Philip Molter wrote:
Attached is a patch that fixes the issue. Given the way that freeradius
checks for the ability to write to the logfile, it should perform like
the latter (in my testing, it does exactly that).
The patch does a couple of things:
1) properly handles setuid changes in
Alan DeKok wrote:
Philip Molter wrote:
Attached is a patch that fixes the issue. Given the way that freeradius
checks for the ability to write to the logfile, it should perform like
the latter (in my testing, it does exactly that).
The patch does a couple of things:
1) properly handles
Hi,
Is this a known bug? Is there a workaround other than creating the file
by hand and setting its ownership before starting freeradius?
?? how are you starting this server - the file/directory should be
radiusd:radiusd
and when run it will do the 'correct thing'
alan
-
List
On Jul 16, 2009, at 4:03 AM, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
Is this a known bug? Is there a workaround other than creating the
file
by hand and setting its ownership before starting freeradius?
?? how are you starting this server - the file/directory should be
radiusd:radiusd
On 07/16/2009 08:12 AM, Philip Molter wrote:
On Jul 16, 2009, at 4:03 AM, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
Is this a known bug? Is there a workaround other than creating the file
by hand and setting its ownership before starting freeradius?
?? how are you starting this server - the
John Dennis wrote:
FWIW, in our RPM's we force the creation of the radius.log file with
ownership radiusd:radiusd at installation time before the server even runs.
If you don't force the creation of the file with the right ownership
then I think the issue revolves around when a log message is
John Dennis wrote:
There are various strategies to assure the newly created log file has
the right ownership:
* drop privileges prior to calling fopen()
* call chown() after fclose() at the exit of the logging call.
* pre-create the file if necessary very early during start up.
I think the
With freeradius 2.1.6, I have a configuration such as this in my
radiusd.conf file:
user = radiusd
group = radiusd
When I start up radiusd for the first time, the radius.log file gets
created with 0640 permissions, owned by root:radiusd, instead of
radiusd:radiusd. This doesn't prevent the
9 matches
Mail list logo
