Please bear with us as we move the ml.
--
Luca Gibelli (luca at clamav.net) - ClamAV, a GPL virus scanner
PGP Key Fingerprint: C782 121E 8C3A 90E3 7A87 D802 6277 8FF4 5EFC 5582
PGP Key Available on: Key Servers || http://www.clamav.net/gpg/luca.gpg
Please bear with us as we move the ml.
our primary ml server is back online. Should you encounter any problem,
please contact me or Mike Cathey privately.
Our contacts are on the website.
Best regards
--
Luca Gibelli (luca at clamav.net) - ClamAV, a GPL virus scanner
PGP Key Fingerprint:
On Feb 20, 2005, at 04:24, Luca Gibelli wrote:
Please bear with us as we move the ml.
our primary ml server is back online. Should you encounter any problem,
please contact me or Mike Cathey privately.
Our contacts are on the website.
Best regards
--
That was smooth, never even noticed a hickup...
[6th try to get this sent out.]
I'm using clamav-milter in the default mode (no --external flag). As such, I
see no need to run clamd. But freshclam doesn't like this very much:
freshclam[26975]: ERROR: Clamd was NOT notified: No socket specified in
/usr/local/encap/clamav-0.83/etc/clamd.conf
On Sun, Feb 20, 2005 at 10:47:53AM -0600, Damian Menscher wrote:
[...]
freshclam[26975]: ERROR: Clamd was NOT notified: No socket specified in
/usr/local/encap/clamav-0.83/etc/clamd.conf
may freshclam.conf still contains a 'NotifyClamd directive?
or rather, the invocation of freshclam
Seems to be a problem with the latest software, here's some debug info:
gdb /usr/sbin/clamd
GNU gdb 5.3-20030128 (Apple version gdb-330.1) (Fri Jul 16 21:42:28 GMT
2004)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
Hello,
When upgrading from clamav 0.80 to 0.83, I received 2 new 'warnings' that
I had not seen on previous builds:
checking resolv.h usability... no
checking resolv.h presence... yes
configure: WARNING: resolv.h: present but cannot be compiled
configure: WARNING: resolv.h: check for
[EMAIL PROTECTED] said:
Hello,
When upgrading from clamav 0.80 to 0.83, I received 2 new 'warnings' that
I had not seen on previous builds:
Configure it without curl and see if it repeats. You might want to check
your include path, too. resolv.h is in /usr/include.
dp
[EMAIL PROTECTED] wrote:
When upgrading from clamav 0.80 to 0.83, I received 2 new 'warnings' that
I had not seen on previous builds:
checking resolv.h usability... no
checking resolv.h presence... yes
configure: WARNING: resolv.h: present but cannot be compiled
configure: WARNING: resolv.h:
René Berber wrote:
SNIP!
I didn't have any problem with resolv.h under Solaris 9, to sort that
out you better look into config.log and see exactly what failed.
I have the original resolv.h for BIND 4.9.4 that came with the OS even
though I also have Bind 8.3 installed.
Snippet from
On Sun, 20 Feb 2005 13:34:07 -0500
Dale Walsh [EMAIL PROTECTED] wrote:
Seems to be a problem with the latest software, here's some debug
info:
[...]
Program received signal EXC_BAD_ACCESS, Could not access memory.
cli_bm_addpatt (root=0x2308040, pattern=0x2308020) at matcher-bm.c:62
62
Jon R. Kibler wrote:
Snippet from config.log follows signature paragraph. Using the original resolver libraries on this system. However, running BIND 9.3.x.
The original resolver includes are in: /usr/include/resolv.h
The new resolver includes are in: /usr/local/bind/include/resolv.h
I don't
These are systems I have been able to see ClamAV either crash or
freeze on (can only do gdb on Mac due to access, I own them.) and the
problem appears to be related to the shared library more than anything
else from what I can tell (meaning, if you use the library, it will
crash and I'm
On Mon, 21 Feb 2005 01:39:20 -0500
Dale Walsh [EMAIL PROTECTED] wrote:
These are systems I have been able to see ClamAV either crash or
freeze on (can only do gdb on Mac due to access, I own them.) and the
problem appears to be related to the shared library more than anything
else from
14 matches
Mail list logo
