Message: 3
Date: Wed, 18 Jun 2008 15:23:43 +0300
From: T?r?k Edwin [EMAIL PROTECTED]
Subject: Re: [Clamav-users] Problem with internal logger
(UpdateLogFile = /opt/zimbra/log/freshclam.log).
To: ClamAV users ML clamav-users@lists.clamav.net
Message-ID: [EMAIL PROTECTED]
Content
Message: 2
Date: Tue, 17 Jun 2008 11:01:19 -0300
From: Leonardo Rodrigues Magalh?es [EMAIL PROTECTED]
Subject: Re: [Clamav-users] ClamAV engine is outdated
To: ClamAV users ML clamav-users@lists.clamav.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1;
Hermann T. Ribeiro wrote:
Edwin, the permissions are: 640, owner zimbra, is it right ?
Is zimbra the user freshclam is running as? Check `clamconf|grep User`
If not, then either configure a different directory (in freshclam.conf)
that is owned by the user running freshclam, or
change permissions
Hello list again.
I solve tho problem.
Stupidly I add freshclam line in root's crontab and it was also running for
clamav user cron at the same time!
Sorry for bothering the list.
Nikos
UpdateLogFile /var/log/freshclam.log
LogSyslog yes
If you are using LogSyslog, why do you specify
Hello list.
After upgrade to 0.92 version on a linux server, the cron sending the
following error:
ERROR: Problem with internal logger (UpdateLogFile = /var/log/freshclam.log).
In the cron I have put this line: 7 * * * * /usr/local/bin/freshclam --quiet
In freshclam.conf I have the
nikos wrote:
UpdateLogFile /var/log/freshclam.log
LogSyslog yes
If you are using LogSyslog, why do you specify an UpdateLogFile? I
would only use Syslog; the internal logger is not a good idea.
It locks the log file, so if a freshclam process becomes stuck,
subsequent freshclams complain. (I
: [Clamav-users] Problem with internal logger
On Debian
mail:/# freshclam
ERROR: Problem with internal logger (UpdateLogFile =
/var/log/clamav/freshclam.log)
What can I do?
--
http://www.ilbonzo.org
Skype: ilbonzo.org
___
Help us build
On Dec 5, 2007, at 9:17 AM, David F. Skoll wrote:
Enable LogSyslog instead of using the built-in logger. (While we're
on the topic, removing the built-in logger would be an excellent code
cleanup; there's really no need to reinvent syslog.)
If ClamAV was intended to run only on Unix
Bonzo wrote:
mail:/# freshclam
ERROR: Problem with internal logger (UpdateLogFile =
/var/log/clamav/freshclam.log)
What can I do?
Enable LogSyslog instead of using the built-in logger. (While we're
on the topic, removing the built-in logger would be an excellent code
cleanup; there's
On Debian
mail:/# freshclam
ERROR: Problem with internal logger (UpdateLogFile =
/var/log/clamav/freshclam.log)
What can I do?
--
http://www.ilbonzo.org
Skype: ilbonzo.org
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
Author: Peter Luttrell
Date:
To: clamav-users
Subject: [Clamav-users] Problem with internal logger
I recently upgraded clamav to version 0.88.2 in order to support
amavisd-new, which I'm using with postfix.
Since then, many times the day my root account receives this message:
From
I recently upgraded clamav to version 0.88.2 in order to support
amavisd-new, which I'm using with postfix.
Since then, many times the day my root account receives this message:
From: [EMAIL PROTECTED] (Cron Daemon)
Date: May 29, 2006 6:24:01 PM CDT
To: [EMAIL PROTECTED]
Subject: Cron [EMAIL
On Mon, May 29, 2006 at 07:09:02PM -0500, Peter Luttrell said:
I recently upgraded clamav to version 0.88.2 in order to support
amavisd-new, which I'm using with postfix.
Since then, many times the day my root account receives this message:
From: [EMAIL PROTECTED] (Cron Daemon)
Date:
13 matches
Mail list logo
