Long Child Startup Times

[Darren Benfer]

Jules,

Thank you, yes! This is exactly the case - we use clamAV/clamavmodule. 
Sorry I did not provide this info in my original post. Switching clam 
off makes things as speedy as ever, so I will just endure it across all 
machines until the current RC moves into release.

Thanks, Darren

Julian Field wrote:
  > I'll put a tenner on the fact that you are running the latest 
version of
> ClamAV and are using the clamavmodule scanner.
> It's ClamAV's fault in that case. The current version takes *forever* to 
> load the signatures. Fortunately it only has to do this once in each child.
> You can fix it by either
> 1) Download and run the latest release candidate of ClamAV which 
> apparently has fixed it. This is the most common solution I have seen.
> 2) Wait for the new version of ClamAV and not worry about it for now. It 
> only affects the startup time of each child, not the actual processing 
> speed of ClamAV. This is what I have done.
> 3) Switch to clamd but make sure you are running something to keep an 
> eye on the clamd daemon in case it crashes (I cannot guarantee clamd's 
> stability).
> 
> Jules.
> 
> Darren Benfer wrote:
>> Lately it seems like it takes MS children take forever to start up for 
>> some reason, and my server load climbs to 4-5 while they are doing so. 
>> Anyone else experiencing (or experienced) this? Anything I should 
>> check into for a fix? Worked well for about year, but latest update 
>> for MS started this trend.
>>
>> TIA!
>> Darren @ Serversphere.com
> 
> Jules
>