Sorry to reply to myself, but I was just able to capture this in gdb
(still don't have the offending zip yet):
Program received signal SIGPIPE, Broken pipe.
0x28117dbc in __sys_write () from /usr/lib/libc_r.so.4
(gdb) backtrace
#0 0x28117dbc in __sys_write () from /usr/lib/libc_r.so.4
#1 0x2810e
I started seeing some Zip module failures that are causing my clamd to die
- I upgraded from 0.65 to the 20031206 snapshot and still had failures:
Dec 6 22:18:07 manganese clamd[2813]:
/var/spool/MIMEDefang/mdefang-hB73I3rv003167/Work/msg-64706-369.zip: Zip
module failure. ERROR
I haven'
Hi
CONFIGURE_ARGS= --with-dbdir=${DATADIR} \
--disable-clamav \
--enable-bigstack \
--with-user=qmailq \
--with-group=qmail
CFLAGS+=-I${LOCALBASE}/include
LDFLAGS+= ${PTHREAD_LIBS}
CONFIGURE_ENV+= LDFLAGS="${LDFLAGS}"
MA
Steve Crowder wrote:
Hi
Anyone know a fix for this error? Is there some Makefile editing required?
/ports/security/clamav/work/clamav-0.65/libclamav
/usr/local/lib/libclamav.so -lz -lbz2 -lc_r -Wl,--rpath -Wl,/usr/local/lib -
Wl,--rpath -Wl,/usr/local/lib
clamscan.o: In function `clamscan':
clam
Hi
Anyone know a fix for this error? Is there some Makefile editing required?
/ports/security/clamav/work/clamav-0.65/libclamav
/usr/local/lib/libclamav.so -lz -lbz2 -lc_r -Wl,--rpath -Wl,/usr/local/lib -
Wl,--rpath -Wl,/usr/local/lib
clamscan.o: In function `clamscan':
clamscan.o(.text+0x7f): un
Graham Murray <[EMAIL PROTECTED]> writes:
> The above error message, followed by a 451 reject, has started
> happening with the CVS version within the last few days. I am not
> sure exactly which version introduced this.
Further investigation shows that fetching CVS of 4 days works
OK. This is in
My clamav.conf looks like this:
linux:/etc/clamav# cat clamav.conf
#To reconfigure clamd run #dpkg-reconfigure clamav-daemon
LocalSocket /var/run/clamd.ctl
ScanMail
ScanArchive
StreamSaveToDisk
StreamMaxLength 50M
ArchiveMaxRecursion 5
ArchiveMaxFiles 1000
ArchiveMaxFileSize 10M
ThreadTimeout 180
M
The above error message, followed by a 451 reject, has started
happening with the CVS version within the last few days. I am not
sure exactly which version introduced this.
The strange thing is that most emails pass through perfectly. With
emails using IPV6, the first one (after restarting clamav
I am using the 12/5 snapshot and while it certainly fixed my compile issues
(thanks..) setting clamd to useProcess causes some concern...
I am running solaris9 and noticed that as the process stops, it is left in
a state...I have many of these and they dont seem to ever go away...
pkill clamd
On Saturday 06 December 2003 12:27 pm, Christoph Barlag wrote:
> Hi!
>
> After the last update of viruses.db2 I got the following error message:
>
> "clam_scanner: corrupt or unknown ClamAV scanner/resource problems - exit
> status 50"
>
> I am using a qmail/qmail-scanner/clamav system.
>
> The pr
Hi!
After the last update of viruses.db2 I got the following error message:
"clam_scanner: corrupt or unknown ClamAV scanner/resource problems - exit
status 50"
I am using a qmail/qmail-scanner/clamav system.
The problem ist cleary not correlated to any softlimit or something. I had
the same
11 matches
Mail list logo