| > | 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. | | > I'm suggesting instead, that a comment is added at the top of | > clamd.conf to clarify why the value is "0". Your explanation was | > clear, but that wasn't obvious from the install. | | I won't do this. The config file is generated by debconf, and as such, | it is the bare minimum of directives to give you a sane initial install. | If you don't like the initial config file, you are free to edit it in | any way you like.
I would rather see that things are transparent. The reason I wrote a bug report was that the value 0 was puzzling. I'm sure someone else could wonder that too. 1) The manual page sugges 1M (on absense) ... but config file contains 0? 2) There are no comments in config file to explain why it needs default value 0 (compared to the default value in manual), especially when the value is not deconf-enabled/handled. You explained 0 in previous mail well. I'm not familiar with debconf, but there already are command in the default clamd.conf, so I don't see an objection why couldn't there be one line more? Is the problem preserving user changes, then the lines could be tagged if the scripts need to parse the file. # debconf-comment 1: .... # debconf-comment 2: .... Anyway, IMO it would be more transparent to the end user if he could see "ah, that's why 0 is in there." Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
