Re: [Clamav-users] Directory recursion limit exceeded error in clamd.log file (clamav version 0.80)
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
Re: [Clamav-users] Directory recursion limit exceeded error in clamd.log file (clamav version 0.80)
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
Re: [Clamav-users] Directory recursion limit exceeded error in clamd.log file (clamav version 0.80)
On Tue, 25 Jan 2005 at 6:42:33 -0700, Hal Goldfarb wrote: On Monday 24 January 2005 05:21, Tomasz Papszun wrote: 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?), [...] 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. 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. clamdscan has _no_ -r option. This is a brand new, first time installation of clamav. Could this be a memory leak of some kind? I doubt it. Try to experiment with setting other values of MaxDirectoryRecursion (and don't forget to reload the clamd). Also, try to reproduce the error in some other, nested directories (e.g. created for testing purposes). -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only [EMAIL PROTECTED] http://www.lodz.tpsa.pl/iso/ | ones and zeros. [EMAIL PROTECTED] http://www.ClamAV.net/ A GPL virus scanner ___ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
[Clamav-users] Directory recursion limit exceeded error in clamd.log file (clamav version 0.80)
Please forgive me if I somehow missed the answer to this question. I did thoroughly search all of the mail archives (including gmane, gossamer, etc) and though some of the tools have somewhat decent search criteria available, I was unable to find a solution. I was hoping not to have to post anything. 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?), 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. Searching through the mail archives, I found some similar errors that were corrected in later releases of clamav, per the mailing list responses. These were back in 2003; I did not see any more recent message posts. (In fact, I only found 5 matches for the exact error message.) Again, I apologize to all if I somehow missed a message addressing this issue. A sidenote: The clamdscan program disregards many clamscan options because it uses the daemon. The -r option is needed for clamscan or it does not scan 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. Thank you, Hal PS How rude of me! I forgot to say: Excellent software set. I like the idea of being able to protect my Linux boxes from destruction. ___ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Re: [Clamav-users] Directory recursion limit exceeded error in clamd.log file (clamav version 0.80)
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: MaxDirectoryRecursion NUMBER Maximal depth directories are scanned at. Default: 15 How many levels of subdirectories have you got under /home/hal/.tvtime ? Or maybe there is some archive file with many subdirectories? [...] A sidenote: The clamdscan program disregards many clamscan options because it uses the daemon. Sure. Exactly because of that reason, there are only few options for clamdscan (see 'clamdscan -h' for the supported ones). The -r option is needed for clamscan or it does not scan subdirectories. This is intended. 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. 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. Thank you, Hal PS How rude of me! I forgot to say: Excellent software set. I like the idea of being able to protect my Linux boxes from destruction. Thanks :-) . -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only [EMAIL PROTECTED] http://www.lodz.tpsa.pl/iso/ | ones and zeros. [EMAIL PROTECTED] http://www.ClamAV.net/ A GPL virus scanner ___ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
