On 3/16/07, Robert <[EMAIL PROTECTED]> wrote:
On 16 Mar 2007, at 17:20, Zbigniew Szalbot wrote: > Hello, > >> Do you mean it rejects it or tempfails it? A tempfail is a legitimate >> condition when your processes are in a failed state. So too is >> reject, but >> certainly more drastic and likely to create political >> repercussions. Worst >> is to silently drop messages. > > It tempfails them, which is fine when it does not take too long :) > > Thanks! > > -- > Zbigniew Szalbot Continuing the 'fatal error' saga, I also noticed the following in the clamd.log: "Thu Mar 15 05:08:10 2007 -> SelfCheck: Database modification detected. Forcing reload. Thu Mar 15 05:08:11 2007 -> Reading databases from /usr/local/share/ clamav Thu Mar 15 05:10:21 2007 -> ERROR: reload db failed: Unable to lock database directory (try 1)
Is there a .dbLock file in /usr/local/share/clamav when this happens? If so, which process owns it? Silly question: does clamd have write permissions to the database directory? --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
