On Thu, 20 Jan 2005 at 9:01:03 +0800, Daniel Suen wrote:
I have downloaded the 0.80 version yesterday and compiled and run it on
both a Linux machine and a Solaris 9 machine. The following problem is
found on both platforms:-
I have a virus file and I tried scanning it with clamscan,
* John Sullivan [EMAIL PROTECTED] [20050120 16:43]: wrote:
On a FreeBSD server I have just upgraded from Clam-0.80_2 to Clam-0.80_3 via
the ports tree and now Clam will not start. I can see in the log that
everything from the config file is processed fine then the last entry
ERROR:
On Thu, 2005-01-20 at 13:42, John Sullivan wrote:
On a FreeBSD server I have just upgraded from Clam-0.80_2 to Clam-0.80_3 via
the ports tree and now Clam will not start. I can see in the log that
everything from the config file is processed fine then the last entry
ERROR: thrmgr_new
On Thu, 20 Jan 2005 13:42:16 -, John Sullivan [EMAIL PROTECTED] wrote:
On a FreeBSD server I have just upgraded from Clam-0.80_2 to Clam-0.80_3 via
the ports tree and now Clam will not start. I can see in the log that
everything from the config file is processed fine then the last entry
Thanks to all who responded. This is now working.
Not quite sure what the problem was but I removed the packages that I had
installed after the last time I upgrade ClamAV on this server, then removed
and reinstalled Clam. It started first time.
John
Oh, and the tutorial that was recommended on this list a couple of weeks
back is wrong. It calls for StreamSaveToDisk option on clam version
0.80. http://www.technoids.org/clamav-milter.html
The change log for clamav 0.80 says
Mon Sep 20 10:09:55 BST 2004 (njh)
--
* Ed Stover [EMAIL PROTECTED] [20050118 15:32]: wrote:
A little history for you, I have run clamav up till the .7x line died
and the StreamSaveToDisk option has always been there. But for some odd
reason it is excluded from the configuration files that I have seen both
by building clamav0.80
Yay!, clamav-milter is semi-working, it was a PEBCAK error. Whats weird
is, now that it is running it marks every piece of mail that passes
through it as clean even dirty mail (more tinkering should take care of
it). Thanks clamav people, your all gooder. And yes I know that online
material has a
On Thu, 25 Nov 2004 at 15:56:41 -0500, paddy wrote:
I have installed clamav-0.80 according to the instructions contained in
the FairlySecureAnitVirusWiki on a brand new box with OpenBSD 3.6.
Everything went well till I got the part where I Update the virus
database. Upon issuing the
Matt Gourley wrote:
I've just installed ClamAV 0.80 onto a new mail server. It's running
well through daemontools, as the test EICAR virus I send it through
qmail-scanner is caught, marked and quarantined. However, I cannot get
it to log to /var/log/clamd.
/service/clamd/run:
#!/bin/sh
exec
Rick Macdougall wrote:
Matt Gourley wrote:
I've just installed ClamAV 0.80 onto a new mail server. It's running
well through daemontools, as the test EICAR virus I send it through
qmail-scanner is caught, marked and quarantined. However, I cannot
get it to log to /var/log/clamd.
Matt Gourley wrote:
Rick Macdougall wrote:
Matt Gourley wrote:
clamd.conf:
FixStaleSocket
Foreground
LocalSocket /tmp/clamd
LogVerbose
MaxThreads 20
ScanArchive
ScanHTML
ScanMail
User qscand
Hi,
Logfile /dev/stdout (or stderr) in clamd.conf
I tried that. If I do that, I get either:
ERROR:
Rick Macdougall wrote:
Matt Gourley wrote:
Rick Macdougall wrote:
Matt Gourley wrote:
clamd.conf:
FixStaleSocket
Foreground
LocalSocket /tmp/clamd
LogVerbose
MaxThreads 20
ScanArchive
ScanHTML
ScanMail
User qscand
Hi,
Logfile /dev/stdout (or stderr) in clamd.conf
I tried that. If I do that,
Matt Gourley wrote:
Logfile /dev/stdout (or stderr) in clamd.conf
I tried that. If I do that, I get either:
ERROR: Problem with internal logger. Please check the
permissions on the /dev/stdout file.
ERROR: Can't open /dev/stdout in append mode (check permissions!).
or the same for /dev/stderr.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick Macdougall wrote:
| /service/clamd/run:
|
| #!/bin/sh
| exec 21
| exec /usr/local/bin/softlimit -a 4000 \ /usr/local/bin/setuidgid
qscand /usr/local/sbin/clamd
|
|
| /service/clamd/log/run:
|
| #!/bin/sh
| exec /usr/local/bin/setuidgid qscand
Andrej Trobentar wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick Macdougall wrote:
| /service/clamd/run:
|
| #!/bin/sh
| exec 21
| exec /usr/local/bin/softlimit -a 4000 \ /usr/local/bin/setuidgid
qscand /usr/local/sbin/clamd
|
|
| /service/clamd/log/run:
|
| #!/bin/sh
| exec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Gourley wrote:
| Andrej Trobentar wrote:
| Put
|
| exec /usr/local/bin/softlimit -a 4000 /usr/local/sbin/clamd
|
| and
|
| exec /usr/local/bin/multilog t s100 n20 /var/log/clamd
|
| in your startups files (without setuidgid). Works for me
On Thursday 21 October 2004 08:25 am, Forexys Support Center wrote:
Hi
i have a small problems with the 0.80 version ... he don't want start
correctly..
I have:
6616 ?S 0:00 \_ supervise clamd
6707 ?Z 0:00 | \_ [run] defunct
6617 ?S 0:00 \_
On Tue, 19 Oct 2004 14:11:53 -0400, Robin, Rob [EMAIL PROTECTED] wrote:
gcc version 2.95.2. BSDi 4.2 (i hate to be on a dead OS, moving to linux
soon).
LOL. You got that right.
I see anything that still use gcc 2.x as obsolete :)
___
On 10/19/04 17:26, Pete D wrote:
Hello all.
I just upgraded to the new ClamAV 0.80. I use the
clamscan command along with the --leave-temps flag to
generate the main.db and daily.db files. I am using a
SMTP proxy spam program called ASSP that uses these db
files for preliminary virus detection.
Thanks for the great tip! The sigtool command works
beautifully. However, it does make me wonder if there
is a bug with the leave-temps flag.
Thanks again.
--- aCaB [EMAIL PROTECTED] wrote:
On 10/19/04 17:26, Pete D wrote:
Hello all.
I just upgraded to the new ClamAV 0.80. I use the
On Tue, 19 Oct 2004 08:26:36 -0700 (PDT)
Pete D [EMAIL PROTECTED] wrote:
Hello all.
I just upgraded to the new ClamAV 0.80. I use the
clamscan command along with the --leave-temps flag to
generate the main.db and daily.db files. I am using a
SMTP proxy spam program called ASSP that uses
Tomasz,
I posted your response here to the ASSP forum. In the
ASSP documentation, it mentions that ASSP lacks the
ability to block all viruses (I guess that is what
they mean by basic anti-virus filtering). I use
ASSP in combination with a amavisd/clamd setup.
Whatever ASSP doesn't catch, the
Robin, Rob wrote:
All,
Tried to upgrade to ClamAV 0.80 from 0.75.1. Failed to compile it.
~~~ ./configure --prefix=/usr/local/clamav/0.80 's warnings -
configure: WARNING: resolv.h: present but cannot be compiled
configure: WARNING: resolv.h: check for missing prerequisite headers?
On Tuesday 21 Sep 2004 21:41, LOYET Jérôme wrote:
Hello,
In order to make the port for OpenBSD. I'd like to know when the final
release of clamav 0.80 will go out.
That depends upon the number of bug reports against 0.80. Remember that it
is only a release candidate, (i. e. beta).
The
25 matches
Mail list logo
