Touche Mr. OP. My guess is that "most" people run ntop with libpcap and not *flow. I assume (perhaps incorrectly) enough people are running 403 to have experienced this issue, even before release, if it was an issue with a more common libpcap deployment. Could be wrong though! Not sure what the diff would be as far as name/ip resolution is concerned.
----- Original Message ----- From: Rick Jones [mailto:[email protected]] Sent: Wednesday, June 08, 2011 12:12 PM To: [email protected] <[email protected]> Subject: Re: [Ntop] double free or corruption (fasttop) On Wed, 2011-06-08 at 10:30 -0500, Gary Gatten wrote: > Ah yes, I recall this - my bad... > > Interesting, OP mentioned sflow and I'm using netflow. And it isn't necessarily clear that the OP thought it had anything to do with sFlow, he merely mentioned that as part of what was running :) rick _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font> _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
