On Mon, 23 Feb 2009, Noel Jones wrote: > Charles Gregory wrote: >> If the issue is FreshClam conflicting with another script/process which >> is updating 'unofficial' configuration files, why not put the onus onto >> that other script/process? You must be running some sort of cron job in >> order to 'regularly' download the updates for those 'unofficial' files? >> So why not run freshclam as part of that same procedure/job? > > Freshclam<->cron update conflicts do not appear to be the > issue; ie. avoiding conflicts does not appear to prevent the > problem, forcing conflicts does not reproduce the problem.
It has also been stated that Clam Team members cannot reproduce the problem, therefore it would require the OP or someone actually experiencing the error to try the suggested 'fixes'. I was responding to the OP's suggestion by offering the idea that it would be easier to fix the 'secondary script' than to fix the freshclam daemon. Obviously, this fix is conditional upon the problem actually being caused by the supposed conflict. > Duplicating cron functions in freshclam will complicate freshclam > without addressing the problem the OP is trying to solve. If you would please properly read my suggestion, which you have quoted, you will see that I have suggested the exact opposite: Fix the script, and have it run freshclam (not as a daemon, obviously). Obviously this also implies a number of possible tests, such as disabling their secondary script to see if that action halts the occurrence of the errors, etc, etc. - Charles _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
