> 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
> Message-ID: <[EMAIL PROTE
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
>
> 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
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Her
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 speci
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.
nikos wrote:
> 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.
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 configuratio
try
/etc/init.d/clamav-freshclam stop
or
killall freshclam
to stop the hung freshclam process
then try again manually
- Original Message -
From: "Bonzo" <[EMAIL PROTECTED]>
To: "ClamAV users ML"
Sent: Wednesday, December 05, 2007 2:11 PM
Subject: [
On Dec 5, 2007, at 9:37 AM, David F. Skoll wrote:
>> If ClamAV was intended to run only on Unix platforms, you'd have a
>> strong point. But ClamAV also runs on Windows platforms which lack a
>> syslogd :-)
>
> Oh, yeah... I forgot about Windoze. Don't use it, so it slipped my
> mind. :-)
Chuck Swiger wrote:
[Re: Removing internal logger code]
> If ClamAV was intended to run only on Unix platforms, you'd have a
> strong point. But ClamAV also runs on Windows platforms which lack a
> syslogd :-)
Oh, yeah... I forgot about Windoze. Don't use it, so it slipped my
mind. :-)
H
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 platfor
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 re
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
h
> 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
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)
> >
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
Freshclam.log must be owned by clamav, whereas clamscan.log is root owned.
Cheers
Brian
At 06:50 16/10/2002, you wrote:
>Hi guys, I just installed the clamav as a rpm package. It seems that I
>cannot run the freshclam with this options as per in the manual.
>
># freshclam --quiet -l /var/log/cl
* Elliot <[EMAIL PROTECTED]> [20021016 09:05]: wrote:
>
> Hi guys, I just installed the clamav as a rpm package. It seems that I
> cannot run the freshclam with this options as per in the manual.
>
> # freshclam --quiet -l /var/log/clam-update.log
>
> The error is
>
> ERROR: LOGGER Can't open f
Hi guys, I just installed the clamav as a rpm package. It seems that I
cannot run the freshclam with this options as per in the manual.
# freshclam --quiet -l /var/log/clam-update.log
The error is
ERROR: LOGGER Can't open file /var/log/clam-update.log
ERROR: Problem with internal logger
Now,
19 matches
Mail list logo
