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 clamav-users@lists.clamav.net
Sent: Wednesday, December 05, 2007 2:11 PM
Subject:
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
Alex,
We generally start off by submitting well thought out, descriptive questions to
mailing lists specific to the application we are having problems with.
Regards,
Richard
A+, N+, AMBCS, MOS-O
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of alex
Hi.
I get these messages on a regular base in freshclam.log
(These only seem to appear after an upgrade of Fedora AND clamav)
WARNING: Clamd was NOT notified: No socket specified in /usr/local/etc/
Looking into the file /usr/local/etc/clamd.conf I see:
# Path to a local socket file the
