Always whether I install or Update ISPConfig 2 I have Only this one problem. clamscan causes my Server or even Linode's to Spike CPU to 100% and Disc IO to over 6k per second! We have asked in the forums more than once for this. All I Ask is for you to Allow the options for clamdscan vs clamscan when updating or installing. I know many other ppl have the same Issue. The Below Sample is from the ajaxterm after a forced reboot. the Installation re-start ispconfig server after update and immidiatly the ssh sessions will freeze. The change i need to make is one line in: activate the clamd executable is available in /home/admispconfig/ispconfig/tools/clamav/sbin/clamd Code: vi /home/admispconfig/ispconfig/tools/clamav/bin/clamassassin change the CLAMSCAN line to CLAMSCAN=/home/admispconfig/ispconfig/tools/clamav/bin/clamdscan OFC I have an Startup daemons for cland and freshclam they can be seen elseware in this forums.
You can use clamd instead of clamscan, you describe that in your post. Or you use ispconfig 3 instead of ispconfig 2, which uses clamd as default. To avoid the update problem that you desciribe, stop postfix before you update. Ispconfig 2 will not get any new features or config changes anymore as it is the old stable version. It will only get security fixes. The active development is done in the ispconfig 3 branch. You should switch to ispconfig 3 as most users did already.
