[ale] Long lag for command line

[Alex Carver]

I think I may have figured out the lag problem.  ClamAV was still 
running its default config which updates every hour (!).  I don't even 
scan once a week so I certainly don't need an update every hour. 
However, it's not smart enough to abort quickly if there's an I/O issue 
(like a slow mirror) so it just hangs on.

At the same time integrit and rkhunter both take off running (integrit 
once per night and rkhunter once per week).  Both of them were scanning 
clamav's files while clamav had them open to update.  To top that off 
would be all the other disk I/O going on at various times (mysql 
actively handling data requests, me fiddling around at the command line, 
SMART probing the disks, other cron jobs, etc.)

So one big I/O collision later, nothing runs properly.  As soon as I 
killed off clamav's freshclam updater, though, everything took off like 
normal and all the delays went away.  So freshclam seems to be the main 
culprit.

I'm still going to keep an eye on it but for now I killed freshclam's 
daemon mode and put a script into cron.weekly so that it only updates 
once per week.  I also have rkhunter and integrit avoiding the clamav 
databases so I think it'll finally behave.

On 7/2/2013 12:19, Alex Carver wrote:
> Ok, so it hung up again.  I've got a good strace and a bad strace for
> starting up vi.  The good strace shows the whole trace taking about
> three seconds.  The bad strace shows the whole trace taking 20 seconds.