I agree with your arguments, unfortunately i need to use rlm_perl and on the other hand i can`t use rlm_ldap (in all respect is too simple to fulfill our complex tasks). Perl is thread-safe. rlm_perl is thread-safe. Does it mean that more than one thread (freeradius) can use perl code (rlm-perl) in parallel ? Please Is it possible to use rlm_cache as storage previously processed request ( correct or incorrect ) to speed up processing ? Thank you very much. ________________________________________ From: freeradius-users-bounces+peter.balsianok=orange.com@lists.freeradius.org [freeradius-users-bounces+peter.balsianok=orange.com@lists.freeradius.org] on behalf of Alan DeKok [aland@deployingradius.com] Sent: Wednesday, September 03, 2014 4:59 PM To: FreeRadius users mailing list Subject: Re: rlm_cache BALSIANOK, Peter wrote:
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.
I've tested LDAP servers at 10K auth/s. There shouldn't be a need for caching. And FreeRADIUS can talk to LDAP natively. There's no need to use Perl for that.
But perl code has limitation. As I understand, only one thread (locking) can use perl code at the same time.
Perl is thread-safe. rlm_perl is thread-safe.
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.
I would suggest just using the LDAP module. It's simpler, and it works. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html