On 29/09/11 1:07 PM, Kevin Manuel wrote: > Hi, that is good news for us that there is a patch available. Can you > provide some direction as to how we go about applying the patch > "multiline-trap-fix-on-2.2.patch"? We are currently running PacketFence > 1.8.7.
The patch attached in the ticket[1] won't apply cleanly on 1.8.7.. Because: - no centralized $TRAP_PATTERN existed - pf::SNMP::constants didn't exist Backporting to 1.8.7 wouldn't be a big effort (in hours) however we have no plans to do so. If you cannot upgrade and want the patch adapted to 1.8.7 you should consider contacting [email protected]. Thanks, [1] http://www.packetfence.org/bugs/view.php?id=1098 -- 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) ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
