Re: convert steel-belt radius .dct to freeradius dictionary

2008-08-19 Thread Alex Balashov
nteger) r > ATTRIBUTE Utstarcom-UNI-Duplex Utstarcom-VSA(187, > integer) r > ATTRIBUTE Utstarcom-ONU-Admin_status Utstarcom-VSA(188, > integer) r > ATTRIBUTE Utstarcom-ONU-FW-SC-Upgrade Utstarcom-VSA(189, > integer) r >>>EO

Re: Crash on x64?

2008-08-18 Thread Alex Balashov
ould possibly be different is the precise glibc2 revision. -- Alex Balashov Evariste Systems Web: http://www.evaristesys.com/ Tel: (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Crash on x64?

2008-08-15 Thread Alex Balashov
;s fine. 2.0.5 (tried both from binary and source0. Postgres 8.3.3. -- Alex Balashov Evariste Systems Web: http://www.evaristesys.com/ Tel: (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Crash on x64?

2008-08-14 Thread Alex Balashov
d-2.5.so 2ac95304d000-2ac95304e000 rw-p 0001b000 fd:00 2193651 Program received signal SIGABRT, Aborted. [Switching to Thread 1129613632 (LWP 11665)] 0x2ac9541e8155 in raise () from /lib64/libc.so.6 Any idea what gives there? -- Alex Balashov Evariste Systems Web: http://www.evaristesys.

Re: Crash on x64?

2008-08-14 Thread Alex Balashov
Alex Balashov wrote: Greetings, I am running a very high-volume FreeRADIUS installation on RHEL 5 (not my choice), and noticed that FreeRADIUS was periodically dying after instantiating a great many worker servers. I looked at the output in GDB and got: Continuing. [New LWP 11400

Crash on x64?

2008-08-14 Thread Alex Balashov
libdl? -- Alex -- Alex Balashov Evariste Systems Web: http://www.evaristesys.com/ Tel: (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

rlm_perl bug?

2008-08-08 Thread Alex Balashov
every clone invocation, so if the problem were simply that the module wasn't there, it would fail immediately. Instead, it happens once in a blue moon. The RADIUS server then stops and must be manually restarted. Any idea why? Thanks much! -- Alex Balashov Evariste Systems Web