Rick,

I think sounds like the problem I had with regex in a previous post 
"Subject: clamscan does not terminate on specific       HTML    file"


- down load and install PCRE I got it from freeware:
        
ftp://ftp.virginmedia.com/sites/ftp.sunfreeware.com/freeware/sparc/10/pcre-7.2-sol10-sparc-local.gz

   replace *regex.h for pcreposix.h in all the following files:
        # grep -l "include.*regex\.h" */*.c */*.h
        clamav-milter/clamav-milter.c
        clamscan/others.c
        libclamav/regex_list.c
        libclamav/phishcheck.h

        # LIBS='-lpcreposix -lpcre' LDFLAGS='-L/usr/local/lib -R/usr/local/lib' 
./configure
        # make
        # make install




rick pim wrote:
> Rob MacGregor writes:
>  > Maybe you meant to include some actual technical details, like O/S,
>  > version of clamav installed etc (and possibly why you restart sendmail
>  > and clamd daily)?
> 
> it wasn't me that reported it, but i'm on the verge of doing the
> same thing. here's why:
> 
> environment: solaris 5.10, sparc 420R (4x450MHz CPU, 4 GB RAM), 
>   sendmail 8.14.1, clamav 0.91.2.
> 
> clam was compiled with the stock (ie installed with the OS) solaris
> 5.10 gcc (3.4.3). the configuration was done with:
> 
> ./configure --prefix=/export/home/clamav --enable-milter
> 
> and clamd.conf looks like:
> 
> LogTime yes
> LogSyslog yes
> LogFacility LOG_MAIL
> TemporaryDirectory /export/home/clamav/tmp
> LocalSocket /var/clamav/clamd.sock
> FixStaleSocket yes
> MaxConnectionQueueLength 32
> StreamMaxLength 64M
> MaxThreads 64
> SelfCheck 3600
> User clamav
> ScanMail yes
> 
> everything works fine for a while -- something more than 8 hours -- with
> CPU usage normally being <10%. sometime overnight, however, it started to
> climb. this morning it was holding steady at about 88%. i stopped sendmail,
> stopped clmilter, stopped clamd and waited.
> 
> after five minutes, clamd was still running at 88% CPU so i fed it a
> kill -9, cleaned out the temp directories, and restarted everything.
> everything looks 'normal' right now.
> 
> we first ran into this issue on an older box when we tried to upgrade
> from 0.88.7. there's been a lot of water under the bridge since then
> with clam, and this is a new box (well, newer) with fresh installs of
> everything. things are better than they were -- six months ago it
> would blow up within an hour or so -- but the performance issues on
> solaris clearly still haven't been licked.
> 
> if we can control it with a once-a-day restart, that'll be workable.
> 
> 
> rp
> 
> rick pim                                           [EMAIL PROTECTED]
> information technology services                          (613) 533-2242
> queen's university, kingston   
> -----------------------------------------------------------------------
> "Normal people bore me -- I prefer lunatics. At least the lunatics are
> committed."
>                     -- Batman Returns
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://lurker.clamav.net/list/clamav-users.html
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

Reply via email to