BALSIANOK, Peter Peter.BALSIANOK at orange.com
Wed Sep 3 16:32:39 CEST 2014


Maybe I didn`t write it correct.
At this moment i`m using rlm_perl to do everythink. 
The perl code also contains internal cache to prevent contact LDAP server (each time). So I can process request quicker.
But perl code has limitation. As I understand, only one thread (locking) can use perl code at the same time. 
Of course I can use more than one perl module instances, but I don`t want.
Therefore I want to use rlm_cache to store reply&control for request, so I don`t need to call perl code if request was correct / incorrect last time.

-----Original Message-----
From: freeradius-users-bounces+peter.balsianok=orange.com at lists.freeradius.org [mailto:freeradius-users-bounces+peter.balsianok=orange.com at lists.freeradius.org] On Behalf Of Alan DeKok
Sent: 3. septembra 2014 16:01
To: FreeRadius users mailing list
Subject: Re: rlm_cache

BALSIANOK, Peter wrote:
> I`m playing with rlm_cache. I want to cache auth request to speed up 
> future processing of the same auth request.

  That probably isn't useful.

> update {
>         request: := &request:
>         control: := &control:
>         reply: := &reply: 
> }

   That isn't useful.  You're caching the *request*?  i.e. over-writing the *new* request with the *cached* one?

  Why would you ever do that?  It makes no sense.

  Alan DeKok.
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

More information about the Freeradius-Users mailing list