In response to Ming Tang mtan...@comcast.net:
I did not find any other error messages in log files. The following lines
appeared in the section for kernel log messages in daily email message for
Security Run Output.
pid 840 (freshclam), uid 1#: exited on signal 11
This is a segmentation
exactly.
Thanks.
- Ming
-Original Message-
From: Bill Moran [mailto:wmo...@potentialtech.com]
Sent: Sunday, March 01, 2009 6:37 PM
To: Ming Tang
Cc: freebsd-questions@freebsd.org
Subject: Re: ClamAV execusion died without error messages
Ming Tang mtan...@comcast.net wrote:
Bill
Ming Tang mtan...@comcast.net wrote:
Bill,
Thank you for the response.
I tried and did not figure out where is the problem. I am attaching the
command line prompts and clamd.log and freshclam.log content here.
ns1#
ns1# ./clamav-clamd.sh status
clamav_clamd is not running.
ns1#
(OS: freebsd5.4, ARCH: i386, CPU: i386)
Thanks.
- Ming
-Original Message-
From: Bill Moran [mailto:wmo...@potentialtech.com]
Sent: Friday, February 27, 2009 1:57 PM
To: mtan...@comcast.net
Cc: freebsd-questions@freebsd.org
Subject: Re: ClamAV execusion died without error messages
My server is currently running on FreeBSD 5.4-RELEASE #0.
I installed the port software, P5-Mail-ClamAV with sendmail along with
others: Spamassassin and Milter etc. Everything was compiled fine, and
sendmail is working with Spamassin too. However, when I
execute clamav-clamd.sh,
In response to mtan...@comcast.net:
My server is currently running on FreeBSD 5.4-RELEASE #0.
I installed the port software, P5-Mail-ClamAV with sendmail along with
others: Spamassassin and Milter etc. Everything was compiled fine, and
sendmail is working with Spamassin too.
