Hello Romain,
this is almost certainly the SQL Trace 4 infinite recursion problem that was
fixed in version 3.1.
Cheers.
On Sat, 1 Jun 2002 08:44, Hugh Irvine wrote:
> Salut Romain -
>
> Quel plaisir de pouvoir regarder le tennis a Roland-Garros en ce moment!
>
> :-)
>
> (ayant vecu a deux pa
Salut Romain -
Quel plaisir de pouvoir regarder le tennis a Roland-Garros en ce moment!
:-)
(ayant vecu a deux pas du stade )
I have copied Mike on this mail, but have you tested the same scenario with
Radiator 3.1? I know there has been some work done in this area.
Please let me know i
Hello Fred -
This is from "Radius/ServerConfig.pm" - it is the list of statistics that are
used when replying to a "Status-Server" request in "Radius/Client.pm":
# These are the official names and descriptions of various statistics
# we keep in each object listed in $p->StatsTrail
%Radius::Ser
Title: Message
If you have some customers that are limited by time and some that are not, you
will need to setup multiple "AuthBy" clauses (1 for each type). I would
recommend using handlers and also setting some sort of "ReplyAttribute".
Something like "CLASS=LIMITED and CLASS=UNLIMIT
Hey guys
Thanks for all the material, I implemented the stuff from goodies/block.txt , but my AuthSql is
still implementing even though when I get
Time_left value is
negative. Isn’t it not supposed to not authenticate for negative values?
Thanks
Jack
Hi
When doing a radpwtst with -status, what does the line with "Dropped access requests"
mean? Is this the number of access-request rejects?
:)
fred
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsub
Hello Hugh, Mike, everyone,
I use Radiator 3.0 together with MySQL on Slackware 8.0 servers.
I noticed that Radiator badly manages the loss of MySQL server ; in certain
cases,
Radiator consumes all available memory then crashes down.
I set up a test server and it was easy to reproduce the proble
