Paul Schmehl wrote:
I've been told that a memory leak in the stream4 preprocessor was fixed in the 2.6.0 release. So you may want to update to that now, or comment it out until the maintainer updates the port. (That port is usually pretty well maintained, so I suspect it won't be long before it's updated.)I'm having the exact same problem on 6.0/amd64. I commented out the stream4 preprocessor lines in the snort.conf file and the problem went away. I just uncommented them this morning, to confirm that that is what is causing the problem.It appears that there is a memory leak in the stream4 preprocessor, but before I report it, I want to confirm that the symptoms are repeatable.
-- Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Description: S/MIME Cryptographic Signature