> > > On Mon, 24 Jan 2005 at 3:04:22 -0700, Hal Goldfarb wrote: > > > > [...] > > > > 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?), >>>>> [...] > > Could this be a memory leak of some kind? > > I doubt it. >
Why do you doubt it? Memory leaks are a common problem in C and C++, even if one is an expert coder. Do you doubt it because you are using a standard set of routines? Even so, could it still be the case that the mainline code is corrupting something in those routines? I suppose I could do something courageous ... like, uh ... get the source code and uh ... do some debugging (yeccch). I just offered a possible explanation for this behavior. > Try to experiment with setting other values of MaxDirectoryRecursion > (and don't forget to reload the clamd). Are there certain values of MaxDirectoryRecursion that work better than others? > Also, try to reproduce the error in some other, nested directories (e.g. > created for testing purposes). Aha! Sounds like you want me to do some debugging for you. Sounds like maybe you are drafting me for some work here ... :D -Hal _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
