Tomasz Kojm wrote:
On Fri, 06 Oct 2006 11:32:52 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
Tomasz Kojm wrote:
On Fri, 06 Oct 2006 10:59:58 +0100
Nigel Horne <[EMAIL PROTECTED]> wrote:
I have found that starting concurrent copies of freshclam can give logg()
errors, but I'm yet to find it resulting in anything crashing. The logg
problems are, I suspect, because of issues in the logfile locking code,
which it's true should be addressed.
What about "LogFileUnlock yes"?
The inference from the comment "the lock protects against running clamd
multiple times" is that one should not use that option. Having said that it
doesn't mention about protecting against multiple copies of freshclam.
This doesn't answer my question. Does "LogFileUnlock yes" added to
freshclam.conf solve the issue?
That's because
1) LogFileUnlock goes in clamd.conf. If freshclam.conf also supports
LogFileUnlock then that should be documented in the freshclam.conf that
is included with the distribution.
[EMAIL PROTECTED] ~]$ cd src/clamav-devel/etc
[EMAIL PROTECTED] etc]$ fgrep -i unlock *.conf
clamd.conf:#LogFileUnlock yes
[EMAIL PROTECTED] etc]$
2) The comment tells you to avoid enabling it!
--
Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter.
NJH Music, Barnsley, UK. ICQ#20252325
[EMAIL PROTECTED] http://www.bandsman.co.uk
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
