Hans-Peter Fuchs wrote:
Hello Alan,
freeradius-2.1.1 created the socket with 'radiusd' as owner and
freeradius-2.1.3 throw error:
Error: We do not own /var/run/radiusd/radius1.sock
because it created it with owner root.
This is a bug in 2.1.3 that will be fixed in 2.1.4.
Alan DeKok.
Hello Alan,
today I upgraded from freeradius-2.1.1 to 2.1.3 and stumbled because
freeradius does not erase the socket file in /var/run/radiusd.
--
Mit freundlichen Grüßen
Hans-Peter Fuchs
Hans-Peter Fuchs - RRZK Zimmer 20
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Hans-Peter Fuchs wrote:
today I upgraded from freeradius-2.1.1 to 2.1.3 and stumbled because
freeradius does not erase the socket file in /var/run/radiusd.
What kind of stumble?
The socket file isn't erased automatically when the server exits. If
something *forces* the server to exit
Hello Alan,
freeradius-2.1.1 created the socket with 'radiusd' as owner and
freeradius-2.1.3 throw error:
Error: We do not own /var/run/radiusd/radius1.sock
because it created it with owner root.
Am Donnerstag, den 29.01.2009, 14:19 +0100 schrieb Alan DeKok:
Hans-Peter Fuchs wrote:
today I
Hi,
Is there a procedure to follow to ask for a new feature to be added?
I seem to have some sort of anomoly that sqltrace is active in my server
even though its not in debug mode. Thats not a big deal.
What I would like, though, is in src/modules/rlm_sql/sql.c for a
Hi,
Is there a procedure to follow to ask for a new feature to be added?
ask here :-)
I seem to have some sort of anomoly that sqltrace is active in my server
even though its not in debug mode. Thats not a big deal.
no. that'll be right. sqltrace is nothing directly to do
Tuc at T-B-O-H.NET [EMAIL PROTECTED] writes:
Is there a procedure to follow to ask for a new feature to be added?
AFAIK:
- develop a patch
- create a bug report requesting the new feature
- attach the patch to the report
I seem to have some sort of anomoly that sqltrace is
I seem to have some sort of anomoly that sqltrace is active in my server
even though its not in debug mode. Thats not a big deal.
no. that'll be right. sqltrace is nothing directly to do with server
debug mode - its a debug mode of the sql module - its enabled and disabled
in sql.conf
Tuc at T-B-O-H.NET [EMAIL PROTECTED] writes:
Is there a procedure to follow to ask for a new feature to be added?
AFAIK:
- develop a patch
- create a bug report requesting the new feature
- attach the patch to the report
Only issue with that is sql.c is written in,
Tuc at T-B-O-H.NET wrote:
I seem to have some sort of anomoly that sqltrace is active in my server
even though its not in debug mode. Thats not a big deal.
no. that'll be right. sqltrace is nothing directly to do with server
debug mode - its a debug mode of the sql module - its enabled
Tuc at T-B-O-H.NET wrote:
I seem to have some sort of anomoly that sqltrace is active in my server
even though its not in debug mode. Thats not a big deal.
no. that'll be right. sqltrace is nothing directly to do with server
debug mode - its a debug mode of the sql module - its
Tuc at T-B-O-H.NET wrote:
WHILE ON THE SUBJECT, it looks like it opens the file, writes, and
closes
it. Does this mean I can move the file nightly without sending radius any
signals,
and the next time it goes to write to it it'll create a new file?
Yes.
Alan DeKok.
-
List
2) Reject Cause (feature request)
Free radius is not informing when it rejects any user if found a
condition false in radgroupcheck or in radcheck only send reject
(reply:Packet-Type), is it possible to give reject with
attributes so
we will know which attribute is the cause
Lucas Aimaretto [EMAIL PROTECTED] wrote:
This is interesting. How can I use Reply-Messages?. In the radreply
table ??? I believe this table is only used if user got an
access-accept, is it true ?
No. It's used during authorization, before the server has decided
if the user is accepted or
the correct way to do this ?
2) Reject Cause (feature request)
Free radius is not informing when it rejects any user if found a condition
false in radgroupcheck
or in radcheck only send reject (reply:Packet-Type), is it possible to give
reject with attributes
so we will know which attribute is the cause
luck then I found it can be done by doing this
1 | babar | Calling-Station-Id | =~ | 0212929234|0212229234
Whats the correct way to do this ?
That works.
2) Reject Cause (feature request)
Free radius is not informing when it rejects any user if found a
condition false in radgroupcheck
Hi Freeradius developers,
A request feature in coming version of Freeradius
Facility to specify alternative name to table nas should be
provided.
Amit Gupta
Anson Rinesmith [EMAIL PROTECTED] wrote:
I would love to see a feature for logging by either realm, client,
or even by CLID. Does the newer FR (.9) having where radius.log can
be sent to a DB instead?
No.
To log by realm/client/whatever, I suggest to change src/main/log.c,
so that
:14 AM
To: [EMAIL PROTECTED]
Subject: Re: feature request
Edgars [EMAIL PROTECTED] wrote:
is it possible somehow to make that for each host there will be separate
radius log file? If no - could ir be likea future feature.
Sure. It's probably 10 lines of code or so in src/main/log.c
Hello!
is it possible somehow to make that for each host there will be separate
radius log file? If no - could ir be likea future feature.
I need this because of very big log file which data i'm using in the
web interface. And each time someone wants to see theese logs for
certain host, i
Graeme Hinchliffe [EMAIL PROTECTED] wrote:
I have a requirement where for a request from a particular pool of
NASes I need to return 3 entries identical every time, and the 4th entry
needs to be one from a list of 10, chosen randomly (or in sequence) as
long as typically a different one
Hiya
having a real good go at optimising our radius servers these last few
days :)
I have a requirement where for a request from a particular pool of
NASes I need to return 3 entries identical every time, and the 4th entry
needs to be one from a list of 10, chosen randomly (or in
Hi,
if you are interested I wrote a patch of rlm_sql.c that logs failed query,
but is not configurable. Just logs to radius.log the failed query if it fails.
Andre
At 16.47 08/06/2004, you wrote:
Hiya
To assist with debugging, could we have an option similar to the
sqltrace, but which
Hiya
To assist with debugging, could we have an option similar to the
sqltrace, but which only logs failed SQL queries? or perhaps logs all
queries for a request if one should error?
I am seeing very infrequent errors, but running sqltrace doesn't help as
I am also getting a LOT of
24 matches
Mail list logo
