>> yes, there is a memory problem under certain circumstances, we cannot
>> track down currently. Therefore I reopened 1.4.1 again and
>> recommmended 1.3.9.1 to be published to SF. Do you have a 1.4.1
>> without this?
>>
>>
>
 >Just to chime in I think this is related to Clam scanning. 
> I saw something very similar when I upgraded to 1.4.1 here 
> and ended up just disabling clamav scanning since I had upgraded 
> that at the same time from the old w32.clamav.net version to 
> the http://oss.netfarm.it/clamav/ version. At this point I'm wondering if
the 
> problem wasn't the new clam version but instead was this memory leak. 
> In any case disabling clam scanning fixed it.

Nope. I do NOT use clamav on that server.

So it's not the clamav, maybe the libraries. I did a little investigations,
since I run the perl modules setup script I have all the libs even the
un-needed ones. I have clamav scanning disabled, (clamav is not even
installed on the server) BUT when I start assp there's an error about clamav
not found. (Cannot connect to unix socket '/tmp/clamd':) 

But I think that's just a cosmetic issue (do not return an error, UseAvClam
is set to off !)


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to