This one time, at band camp, Jari Aalto said: > debconf does not seem to ask details for LogFileMaxSize, but it would > be good it it did, since overly long log files are not good. > > Perhaps a more sensible default could be used in clamd.conf as well, > like: > > LogFileMaxSize 2000000 # approx. 2M
Debconf does not need to be abused for things that have good defaults. In this case, a good default is to not restrict the size of the logfile, but rotate it relatively often. This is exactly what the package does on a default install - setting LogFileMaxSize to 0 disables truncation of the log file, and a logrotate file is set up automatically. If you need to restrict the size of the log file, feel free to do so. It will be respected on upgrade. Since I don't think this is a bug, but rather a design decision, I am inclined to close it. However, I am willing to leave it open but tagged as wontfix so a future maintainer can decide if they want to do it this way. If I hear from you in the next week, I will tag it appropriately and adjust the severity. Otherwise, I will just close this bug. A final note - sending bug reports from an email address that bounces makes it very difficult to work with you to fix the bugs you report. So far, we have been lucky, and both of the reports have not been bugs. If you hit on something that will need your assistance for debugging, it will be impossible. PLease fix your mail client to send with a real email address. Thanks for the report, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
pgpm176gCNFc5.pgp
Description: PGP signature
