Robert Zilbauer <[EMAIL PROTECTED]> > On Wednesday 13 September 2006 05:43, Dennis Peterson wrote: > > > Here too, updates stopped on august 16th. > > > > > > On 6 out of 6 mailservers running clamav, something went very wrong on > > > august 16th. > > > > I run freshclam out of cron so would never have had this problem. I see > > failures all the time - 'Mirrors not fully...', etc., but it finally > > gets a fresh pattern. > > Ditto. I used to run all of my freshclam procs as daemons. However, a while > back I switched all of our machines (mostly Solaris 9 & 10, sparc) running > freshclam to use a cron job instead of daemon mode. > > As of 0.88.1 I began seeing a "silent death" problem in the freshclam daemon > (it seemed to die with a SIGPIPE). Mine was a somewhat different issue than > the problem reported today as I never had a freshclam process just hang and > do nothing. If mine choked, they died completely. > > In my experience, freshclam in cron is the way to go. I haven't had any > trouble with it whatsoever since I switched.
I am running FreshClam on a FreeBSD 6.1 O without any problems. I routinely check the logs twice a week and nothing out of the ordinary is ever reported. I try to stay away from CRON whenever possible. There is always the possibility that I might forget to enable or disable something. Enabling or disabling in etc/rc.conf works just fine for me. I just let it run as daemon. Perhaps there is something else wrong on your OS. If this was really a software bug, then everyone, or at least a large number of users would be suffering this problem. I see no evidence of that anywhere. Perhaps an out of date library is screwing things up. -- Gerard Seibert [EMAIL PROTECTED] I went to a Palestinian SEX-SHOP the other day and bought a life-sized doll. When I got her home, she blew herself up. _______________________________________________ http://lurker.clamav.net/list/clamav-users.html