[LogFileMaxSize] | > Yes, the behavior of 0 is explained there. The confusion arose, when | > it was explicitly set. I waould have expected the manual page's | > default value. Thus the question: "Why the defaul configuration uses | > 0?" | | I have to think in terms of what is a sane | default on first install, and then respect user changes to those defaults | on upgrade.
Fair enough. | The problem is that adding commented explanations for every file option | and combination will create a huge maintenance nightmare, it would seem | to me. Again, I am willing to accept patches to make it happen. But, | I want to caution - this should be done for all directives, or none. | A partial patch will just lead to more people asking for the same thing | for other directives, and a piecework approach seems wrong. If you want | a heavily commented config file, choose no to debconf configuration, | and take a look at the one in /usr/share/doc/clamav-base/examples/. I would like to propose another solution. - Add a comment to the beginning of clamd.conf to point people to read /usr/share/doc/README.DEbian for changes to variables that differ from the defaults outlined in the manual page / upstream. - In /usr/share/doc/README.DEbian there would be section "clamd.conf changes to upstream" and list of only those variables, whose values have been changed accompanied with a brief reasoning why changes were made. | > Other than that, I do not have expertise on how the upgrade works, or | > how the confguration files are managed, so I'm unable to make better | > suggestions. | | I am not sure what to do. I would like to close it outright, since I | see this as a misunderstanding about the features of the debconf | configuration, rather than a bug. However, if you feel strongly enough | about this issue to supply a patch, let me know. I will in that case | leave the bug open until the patch is merged in and uploaded. A misunderstanding may be bug as well if the medium may not have communicated the idea to the end user well enough :-) Let me know if the above would work from maintenance point of view. In any case I'm out of ideas, so you can close this bug. If I were competent with the packaging I would have provided patches, but as it is now, I cannot suggest anything creative for it. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
