clamd keeps exiting

[Mipam]

On Thu, 15 Jul 2004, Warren Block wrote:

> On Thu, 15 Jul 2004, Mipam wrote:
> 
> > Maybe the program is linked to some libs during compile time, but at
> > running time is uses other libs? I wonder why i seem to be the only one
> > who is running into trouble like this. Big difference with OpenBSD is that
> > FreeBSD 5 does threading and supports SMP, which is applicable for the
> > machine i run clam on. Not that this answer is sensefull, but i wondered
> > if i am the only one experiencing trouble with clamd.
> 
> Is anything logged in /var/log/clamav/clamd.log?
> 
> -Warren Block * Rapid City, South Dakota USA

ls /var/log/clamav/clamd.log yields:

+++ Started at Wed Jul 14 10:30:57 2004
clamd daemon 0.74 (OS: freebsd5.2.1, ARCH: i386, CPU: i386)
Log file size limited to 2097152 bytes.
Verbose logging activated.
Running as user clamav (UID 1006, GID 1007)
Reading databases from /usr/local/share/clamav
Protecting against 22678 viruses.
Unix socket file /var/run/clamav/clamd
Setting connection queue length to 15
Listening daemon: PID: 859
Archive: Archived file size limit set to 10485760 bytes.
Archive: Recursion level limit set to 5.
Archive: Files limit set to 1000.
Archive: Compression ratio limit set to 200.
Archive support enabled.
RAR support disabled.
Mail files support enabled.
OLE2 support enabled.
Self checking every 3600 seconds.

and in var/log/messages

Jul 14 10:33:10 rbns01 kernel: pid 859 (clamd), uid 1006: exited on signal 
6

For the rest i couldnt find anything just this.
I have no clue why it keeps exiting.
The deps:

/usr/local/sbin/clamd:
        libclamav.so.1 => /usr/local/lib/libclamav.so.1 (0x28086000)
        libz.so.2 => /lib/libz.so.2 (0x280ae000)
        libbz2.so.1 => /usr/lib/libbz2.so.1 (0x280bc000)
        libgmp.so.6 => /usr/local/lib/libgmp.so.6 (0x280cb000)
        libc_r.so.5 => /usr/lib/libthr.so.1 (0x280f9000)
        libc.so.5 => /lib/libc.so.5 (0x2810a000)

kern.version: FreeBSD 5.2.1-RELEASE-p9 #3: Thu Jul  8 16:43:50 CEST 2004
Any clues?
I cant seem to get any more debug info about what happend even not with 
the --debug option enabled.
Any hints?
Bye,

Mipam.