Hi there! We have been quite busy, as usual, and we are getting tired of the various freeradius segfaults we have been seeing in large environments.
If you've never experienced one, then don't bother reading the rest of this mail as you won't be able to help us (you don't have the problem). #1377: freeradius segfaults http://www.packetfence.org/bugs/view.php?id=1377 I wonder if anyone of you found a solution for these and would be willing to share? Also, in the ticket I outlined potential things to try out to fix the situation. If one of you would be willing to try these it would help us *a lot*. Of course, the best would be to have a reproducible test case but otherwise: - recompile freeradius and perl together with a stable perl release (> 5.10) - try to make the stacktrace better by compiling freeradius AND perl with debug/symbols enabled - try other rlm_perl debug options as outlined on the freeradius-users list (http://www.mail-archive.com/search?q=debug+rlm_perl&l=freeradius-users%40lists.freeradius.org) If someone helps us fix that one, I'll fix a bug* of his choice! Promise! *: a bug not implement a feature, well, unless it's a small feature ;) -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
