Hi,
I've tried 2.2.4 when it was released. It coredumps all the way with dhcp and rlm_perl while using many hundreds of threads, 2.2.0 is much more stable in our setup and 2.2.4 is unusable.
report the bugs - we run 2.2.4 on busy servers with no issues (touch wood!! crazy to say that on a friday! ;-) ) I'm suprised you arent finding even worse issues on 2.2.0(!)
We use MS SQL database and I need perl DBI to keep persistent pool of database connections.
use 3.0.2 :-)
There is no place to make mistake: tcpdump shows precise timestamps noting moment of request arrival. And then syslogd marks a moment then perl code starts: there is 6 seconds delay in between.
..thats...just weird. we dont get such issues with PERL. are you using the global caching of PERL module? alan