On Tue, 12 Feb 2008 10:33:35 +0100
Heskes, E.H. (Erik) [EMAIL PROTECTED] wrote:
After updating and upgrading debian packages and then restarting the
Clamav Daemon I get:
/etc/init.d/clamav-daemon restart
Starting ClamAV daemon clamd ERROR: Parse error at line 46: Unknown
option
After updating and upgrading debian packages and then restarting the
Clamav Daemon I get:
/etc/init.d/clamav-daemon restart
Starting ClamAV daemon clamd ERROR: Parse error at line 46: Unknown
option PhishingScanURLs.
ERROR: Can't open/parse the config file /etc/clamav/clamd.conf
I tried
Roberto Ullfig wrote:
Török Edwin wrote:
Roberto Ullfig wrote:
This won't work for us. This creates a usr hierarchy starting under DESTDIR.
The installation needs to go into directories like this:
/mnt/aaa/bbb/local/ccc/ddd/bin
/mnt/aaa/bbb/local/ccc/ddd/lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Clam is reporting that one of my MX servers is a 'virus' source. How do
I tell it that the mailhop.org server is innocent and that the source of
the mail is farther up the line?
The infected machine is likely to be here:
from localhost ([127.0.0.1]
Christopher X. Candreva wrote:
On Tue, 12 Feb 2008, shuttlebox wrote:
Maybe you could also try the packages from Blastwave?
http://www.blastwave.org/packages.php/clamav
Wow, this is a switch -- don't we usually tell people they are better of
compiling from source ? :-)
Seriously, do
Roberto Ullfig wrote:
Roberto Ullfig wrote:
Well, it's the final destination for the repository but not for the
actual installations (/usr/local). I suppose I'll need to compile it
twice then, once for each location even though it never gets run from
the repository.
No,
Török Edwin wrote:
Roberto Ullfig wrote:
This won't work for us. This creates a usr hierarchy starting under DESTDIR.
The installation needs to go into directories like this:
/mnt/aaa/bbb/local/ccc/ddd/bin
/mnt/aaa/bbb/local/ccc/ddd/lib
Is that the final destination? If yes
Roberto Ullfig wrote:
This won't work for us. This creates a usr hierarchy starting under DESTDIR.
The installation needs to go into directories like this:
/mnt/aaa/bbb/local/ccc/ddd/bin
/mnt/aaa/bbb/local/ccc/ddd/lib
Is that the final destination? If yes you can use ./configure
Is there a way to run multiple installations at the same time from a
common source directory. make install creates/modifies files in the
install directory itself and the installations mess each other up. I
have 20 servers I upgrade and it would be cool if I didn't need to wait
for one
Roberto Ullfig wrote:
No, that's not going to work since the copy in our repository needs to
be identical to the copy that gets installed in /usr/local. We copy the
files from the repository to /usr/local when we clone a new server.
Will commenting out the 4 lines in libtool break anything?
Roberto Ullfig wrote:
We use a binary repository in blah/local/blah. In the past I would set
prefix and install to this location. This is no longer possible with
0.92.1 (maybe 0.92 also).
export prefix=blah/local/blah
make -e install
...
...
libtool: install: error: cannot install
On Tue, 12 Feb 2008, shuttlebox wrote:
I thought so since I had tried scanning with it and it worked but when
I try to get the version info mine also segfaults. :-(
Interesting -- yes, it does actually scan, just --version causes the
segfault.
Is there any detailed documentation available on the daily.inc files, including
the purpose of each, format/syntax, etc.?
I have searched the archives and the one question that was similar from an
individual on the flags was never responded to, and the links that seem to
point to that sort
We use a binary repository in blah/local/blah. In the past I would set
prefix and install to this location. This is no longer possible with
0.92.1 (maybe 0.92 also).
export prefix=blah/local/blah
make -e install
...
...
libtool: install: error: cannot install `libclamunrar_iface.la' to a
[EMAIL PROTECTED] wrote:
You could try the packages from Blastwave.
http://www.blastwave.org/packages.php/clamav
That doesn't answer the question, however. I would like to reiterate the
original post: why is the FPU endianness test failing,
Probably because the default grep won't
You could try the packages from Blastwave.
http://www.blastwave.org/packages.php/clamav
That doesn't answer the question, however. I would like to reiterate the
original post: why is the FPU endianness test failing, and what features may
not be available because of this? Is it possible
I wrote earlier that
clamscan --version behaves differently in 0.92.1 to 0.92
# clamscan --version
ClamAV 0.92.1
# clamscan --version
ClamAV 0.92/5785/Tue Feb 12 10:41:10 2008
It looks like the checkin to fix bug 699
(https://wwws.clamav.net/bugzilla/show_bug.cgi?id=699) has broken
Török Edwin wrote:
Roberto Ullfig wrote:
We use a binary repository in blah/local/blah. In the past I would set
prefix and install to this location. This is no longer possible with
0.92.1 (maybe 0.92 also).
export prefix=blah/local/blah
make -e install
...
...
libtool: install:
On Tue, 12 Feb 2008, shuttlebox wrote:
Maybe you could also try the packages from Blastwave?
http://www.blastwave.org/packages.php/clamav
Wow, this is a switch -- don't we usually tell people they are better of
compiling from source ? :-)
Seriously, do you have a reason to think this
On Feb 12, 2008 1:43 PM, Christopher X. Candreva [EMAIL PROTECTED] wrote:
On Tue, 12 Feb 2008, Randal, Phil wrote:
clamscan --version behaves differently in 0.92.1 to 0.92
# clamscan --version
ClamAV 0.92.1
I seem to have a bigger problem:
[castor]:~/apps/mail/clamav-0.92.1/clamscan$
On Tue, 12 Feb 2008, Randal, Phil wrote:
clamscan --version behaves differently in 0.92.1 to 0.92
# clamscan --version
ClamAV 0.92.1
I seem to have a bigger problem:
[castor]:~/apps/mail/clamav-0.92.1/clamscan$ ./clamscan --version
Segmentation Fault
Solaris 8, gcc 4.2.2
On Feb 12, 2008 12:55 PM, Jonathan Armitage
[EMAIL PROTECTED] wrote:
I have just compiled ClamAV 0.92.1 on one of our mail servers, a Sun X2100 M2
with an AMD chip, and also on my test machine, an old Dell with a Pentium
chip.
Both machines are running Solaris 10.
In both cases I spotted
On Tue, 12 Feb 2008 12:29:09 +0100
Heskes, E.H. (Erik) [EMAIL PROTECTED] wrote:
It's version 0.90.2-01
This version doesn't support PhishingScanURLs
--
oo. Tomasz Kojm [EMAIL PROTECTED]
(\/)\. http://www.ClamAV.net/gpg/tkojm.gpg
\..._
clamscan --version behaves differently in 0.92.1 to 0.92
# clamscan --version
ClamAV 0.92.1
# clamscan --version
ClamAV 0.92/5785/Tue Feb 12 10:41:10 2008
Can we have the old behaviour back please?
Phil
--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK
On Tue, 12 Feb 2008 10:33:35 +0100
Heskes, E.H. (Erik) [EMAIL PROTECTED] wrote:
After updating and upgrading debian packages and then restarting the
Clamav Daemon I get:
/etc/init.d/clamav-daemon restart
Starting ClamAV daemon clamd ERROR: Parse error at line 46: Unknown
option
I have just compiled ClamAV 0.92.1 on one of our mail servers, a Sun X2100 M2
with an AMD chip, and also on my test machine, an old Dell with a Pentium chip.
Both machines are running Solaris 10.
In both cases I spotted the following line in the output from configure:
checking whether FPU byte
Thanks, I commented out the Phishing lines and it runs again.
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Tomasz Kojm
Verzonden: dinsdag 12 februari 2008 12:34
Aan: clamav-users@lists.clamav.net
Onderwerp: Re: [Clamav-users] Clamav-users] Clamav
27 matches
Mail list logo
