My knowledge IS limited.... Several days ago I posted that my Clamd install was regularly crashing during database reloads. Having changed various options to fix this I find it still crashes but far less frequently.
But I have a theory / question..... I ran the following command to establish db reload times...... " time clamscan /dev/null ERROR: Not supported file type (/dev/null) ----------- SCAN SUMMARY ----------- Known viruses: 1833733 Engine version: 0.95.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 34.569 sec (0 m 34 s) real 0m34.594s user 0m31.786s sys 0m1.061s " So reload times are around the 30 sec mark. Clamdwatch is set to run every minute and it's timeout value is less than 30 secs. Now, if Clamd's db reload and clamdwatch execute at the same time, would clamdwatch timeout before the Clam's db reload had finished ? Would this then cause clamdwatch to assume Clamd had crashed and restart it accordingly ?? If I'm way off base here, be merciful.... Robert _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml