[clamav-users] FreshClam problem | MailScanner setup
mark at meelhuysen.com
Wed Oct 29 17:59:33 EDT 2014
Thank you for your reply. I already posted the question on that forum, but no one knew the answer so they directed me to the ClamAV community. :)
I will try some other communities. :)
From: clamav-users [mailto:clamav-users-bounces at lists.clamav.net] On Behalf Of Shawn Webb
Sent: woensdag 29 oktober 2014 18:38
To: ClamAV users ML
Subject: Re: [clamav-users] FreshClam problem | MailScanner setup
On Wed, Oct 29, 2014 at 12:14 PM, Mark Meelhuysen <mark at meelhuysen.com>
> I recently installed a CentOS system running MailScanner, ClamAV,
> SpamAssassin and greylisting.
> Since I solved another problem, for which I opened many configfiles,
> my freshclam does nto update automatically anymore. My MailScanner
> conf is adjusted so update starts in /usr instead of /usr/local.
> My maillog is filled with following errors:
> ClamAV updater /usr/local/bin/freshclam cannot be run ClamAV updater
> /usr#015/bin/freshclam cannot be run ClamAV updater
> /usr/local#015/bin/freshclam cannot be run
> First line after finishing install. Second line after editing
> virus.scanners.conf (/usr/local to /usr).
> At the third line i changed the line back (for testing) to /usr/local.
> It seems like something is putting #015 in front of it. Maybe i
> mistyped (without realizing) in a file, but I can not manage to find
> the problem file. Hope someone can help.
> Thanks in advance.
I would guess that the problem lies in whatever script or process is calling freshclam. Nothing in ClamAV spits out those kinds of errors.
Please refer to the documentation of the software package you're using that integrates with ClamAV.
Help us build a comprehensive ClamAV guide:
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
More information about the clamav-users