On Monday 24 January 2005 05:21, Tomasz Papszun wrote:
> On Mon, 24 Jan 2005 at  3:04:22 -0700, Hal Goldfarb wrote:
> > [...]
> > I am running Mandrake 10.1 with all mdk updates applied as of this
> > message.  I am running clamav 0.80 with the latest virus database
> > updates.  The RPM is release 5.1.101mdk, to be exact.
> >
> > Problem:  When I run clamdscan (which uses the daemon), it generates
> > zillions of errors in the clamd.log file something like "Directory
> > recursion limit exceeded at /home/hal/.tvtime".  However, when I run
> > clamscan (which does not use the daemon, right?),
>
> Right.
>
> > it does not generate these errors as far as I can tell.
> > I am using the default recursion of 20 levels, so I think I should be ok.
>
> To be precise: according to clamd.conf the default is 15:

Pardon me, you are right.  I was looking at the "default" setting for 
MaxDirectoryRecursion in Mandrake's version of clamd.conf, which is 20, but 
is commented out.

>
>        MaxDirectoryRecursion NUMBER
>               Maximal depth directories are scanned at.
>               Default: 15
>
>
> How many levels of subdirectories have you got under /home/hal/.tvtime ?

That directory is a leaf node.  Just a couple of xml files, not archived or 
compressed.

> Or maybe there is some archive file with many subdirectories?
>
> [...]
>
> > However, clamdscan seems to automatically trigger recursion
> > when calling the daemon to do its work.  This seems asymetrical to me,
> > but perhaps you can educate me why it is this way.
>
> As clamdscan is only an interface to clamd, the way it works depends on
> clamd.conf. To be sure what settings are used for clamd, you have to
> check the contents of clamd.conf. 

OK, I see what you mean:  The MaxDirectoryRecursion  parameter, 
aforementioned, is the symmetric partner of clamdscan's "-r" option.

> Moreover: make sure there are _no_ 
> other - forgotten clamav related files in the system because one may be
> using them instead of these one is thinking is using.
> Check also the clamd.log file (the fragment after "Started at") for
> settings used by clamd.

This is a brand new, first time installation of clamav.

Could this be a memory leak of some kind?

Thanks,
Hal



_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users

Reply via email to