Date: Thu, 15 Jul 2004 07:28:15 -0500 From: uidzero <uidzero@one-arm.com> To: Warren Block <wblock@wonkity.com>, FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: clamd keeps exiting Message-ID: <40F6785F.80702@one-arm.com> In-Reply-To: <20040715052137.Q85683@wonkity.com> References: <Pine.BSO.4.56.0407131727220.8713@ux11.ltcm.net> <200407142059.05816.jaymo@cromagnon.cullmail.com> <Pine.BSO.4.56.0407151030170.12608@ux11.ltcm.net> <20040715052137.Q85683@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" I had issues with clamd doing the samething. I'm running 4.10 and what I did to fix mine was to chown "/var/run/clamd" to vscan to allow amavisd to run it. Maybe it's different for you but, that's what I had to do. Michael -- Michael D. Whities uidzero@one-arm.com http://www.one-arm.com -- There are four colors of hats to watch for: Black, White, Grey, and Red. The meanings are: Cracker, Hacker, Guru, and Victim.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40F6785F.80702>