Garber, Neal wrote:
> Igor: I hope you weren't offended by my assumption - I wasn't sure, based
> upon your comment, and I was just trying to help. If I offended you, I
> apologize. By the way, out of curiosity, did the patch work for you on 2.1.7
> also?
>
Don't worry, i wasn't offended at
> I know how to patch. I was just trying to find out what was the error.
Igor: I hope you weren't offended by my assumption - I wasn't sure, based upon
your comment, and I was just trying to help. If I offended you, I apologize.
By the way, out of curiosity, did the patch work for you on 2.1.7
On Jul 29, 2009, at 9:32 AM, Igor Smitran wrote:
know that Boian is responsible for making our life easier :) I was
asking if this patch is going to be included in next release. That is
the comment i was expecting. Sorry for misunderstanding.
Sure I will pull the changes back to repository.
Garber, Neal wrote:
> The error is in rlm_perl and appears related to thread data management, not
> the O/S and not perl (I run FreeBSD and you run CentOS; we even have
> different versions of perl). Boian can explain the change far better than I
> can; but, my interpretation of the change is t
Ivan Kalik wrote:
> Why? Alan is not the only developer. Read the copyright for rlm_perl code.
I know that Boian is responsible for making our life easier :) I was
asking if this patch is going to be included in next release. That is
the comment i was expecting. Sorry for misunderstanding.
Igor
> I didn't try it yet and i am not very good in C. Error that I and Neal
> had is something regarding OS or...? I don't see anyone else having this
> problem except me and Neal.
The error is in rlm_perl and appears related to thread data management, not the
O/S and not perl (I run FreeBSD and you
> I didn't try it yet and i am not very good in C. Error that I and Neal
> had is something regarding OS or...? I don't see anyone else having this
> problem except me and Neal.
> Also, i didn't see any comment from Alan. If this is something that was
> already been discussed here i am sorry for br
Boian Jordanov wrote:
>
> On Jul 26, 2009, at 12:59 AM, wrote:
>
>> Igor wrote:
>>
>>> I have tried 2.1.7 and got same error. I will try to compile it with
>>> --enable-developer and see if i can find out anything from gdb output.
>>> I realy don't know why would this happen because exactly the s
Behalf Of Boian Jordanov
Sent: Monday, July 27, 2009 10:09 AM
To: si...@blic.net; FreeRadius users mailing list
Cc: Boian Jordanov
Subject: Re: rlm_perl problems]
On Jul 26, 2009, at 12:59 AM, wrote:
> Igor wrote:
>
>> I have tried 2.1.7 and got same error. I will try to compile it with
On Jul 26, 2009, at 12:59 AM, wrote:
Igor wrote:
I have tried 2.1.7 and got same error. I will try to compile it with
--enable-developer and see if i can find out anything from gdb
output.
I realy don't know why would this happen because exactly the same
setup worked on
older releases.
Igor wrote:
>I have tried 2.1.7 and got same error. I will try to compile it with
>--enable-developer and see if i can find out anything from gdb output.
>I realy don't know why would this happen because exactly the same setup worked
>on
>older releases. All i did was to compile the new version (
On Sat, 25 Jul 2009 12:26:42 , sent:
>
>
>On Sat, 25 Jul 2009 00:01 , 'Garber, Neal' neal.gar...@energyeast.com> sent:
>
>>Igor: Can you rebuild FR and look at the output of rlm_perl on
>>your system to see if you see similar errors?
>
I have tried 2.1.7 and got same error. I will try to compi
On Sat, 25 Jul 2009 00:01 , 'Garber, Neal' sent:
>Igor: Can you rebuild FR and look at the output of rlm_perl on
>your system to see if you see similar errors?
I will setup testing 2.1.6 freeradius and try the same configuration on it.
After that i will setup 2.1.7pre and try it again. Since
> Two perl instances running different perl scripts! I would suggest
> following instructions in doc/bugs to find out what is causing the
> segfault.
rlm_perl is acting very strangely on my 2.1.6 test system (beyond what
I've already mentioned). I have two instances of a script called
write_log_
> Garber, Neal wrote:
>> Igor,
>>
>> What version of perl and what O/S are you using? I'm using FreeBSD 7.2
>> with perl 5.8.9. The reason I hadn't submitted this sooner is I wanted
>> to rule out an issue with perl (our Productions servers are running an
>> older version of FreeBSD and perl).
>
Garber, Neal wrote:
> Igor,
>
> What version of perl and what O/S are you using? I'm using FreeBSD 7.2 with
> perl 5.8.9. The reason I hadn't submitted this sooner is I wanted to rule
> out an issue with perl (our Productions servers are running an older version
> of FreeBSD and perl).
perl, v
Igor,
What version of perl and what O/S are you using? I'm using FreeBSD 7.2 with
perl 5.8.9. The reason I hadn't submitted this sooner is I wanted to rule out
an issue with perl (our Productions servers are running an older version of
FreeBSD and perl).
-
List info/subscribe/unsubscribe? Se
Ivan Kalik wrote:
>> It ends with freeradius crashing. If i disable all other perl calls and
>> leave only dummy.pl works with no problems. Same goes for other way
>> around. Basicaly, any combination that involves only one perl script
>> works without any problems. If i use two perl scripts in a
s-bounces+neal.garber=energyeast@lists.freeradius.org]
On Behalf Of Ivan Kalik
Sent: Friday, July 24, 2009 10:43 AM
To: FreeRadius users mailing list
Subject: Re: rlm_perl problems]
> It ends with freeradius crashing. If i disable all other perl calls and
> leave only dummy.pl works w
> It ends with freeradius crashing. If i disable all other perl calls and
> leave only dummy.pl works with no problems. Same goes for other way
> around. Basicaly, any combination that involves only one perl script
> works without any problems. If i use two perl scripts in any combination
> freerad
I've been debating sending a similar message to the list as well. I am also
experiencing the same problem with 2.1.6 (undefined subroutines that *clearly*
exist in the script) and Seg Faults. I have reinstalled perl and then
reinstalled FreeRadius to see if I can work around the issue with no
Ivan Kalik wrote:
>> perl perl_script_1 {
>> module = ${confdir}/config_dialup/perl_script_1.pl
>> func_authorize = authorize_check_username
>> func_accounting = accounting_check_username
>> }
>>
>> perl perl_script_2 {
>>
>> module = ${confdir}/config_dialup/perl_
> Ivan Kalik wrote:
>> Have you defined func_post_auth?
>>
>> Ivan Kalik
>> Kalik Informatika ISP
>>
> Left everything by default. Made script by using example.pl as template.
> Both scripts are looking exactly the same, except that i don't use
> default function names for perl_script_1.
>
> perl p
Ivan Kalik wrote:
> Have you defined func_post_auth?
>
> Ivan Kalik
> Kalik Informatika ISP
>
Left everything by default. Made script by using example.pl as template.
Both scripts are looking exactly the same, except that i don't use
default function names for perl_script_1.
perl perl_script_1
> I am using Freeradius 2.1.6.
>
> I have a working setup of freeradius with perl scripts inside authorize
> and accounting sections.
> Everything works great when i am using only one script.
> But. if i add another script to do some other stuff for example in
> post-auth section i get errors in lo
25 matches
Mail list logo
