This one time, at band camp, Jari Aalto said:
>
> [LogFileMaxSize]
>
> 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
[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 o
Sorry about the long delay in responding. This bug report got buried
under other things, and I somehow forgot about it temporarily.
This one time, at band camp, Jari Aalto said:
> |
> | Just a ping to see what you want to do with this. I feel that it is not
> | necessary to add to debconf, as i
|
| Just a ping to see what you want to do with this. I feel that it is not
| necessary to add to debconf, as it has a sensible default for most
| systems. In the event that you are running clamd on a severely disk
| constrained system, this option can be added manually, and it will be
| preserv
Just a ping to see what you want to do with this. I feel that it is not
necessary to add to debconf, as it has a sensible default for most
systems. In the event that you are running clamd on a severely disk
constrained system, this option can be added manually, and it will be
preserved over upgra
This one time, at band camp, Jari Aalto said:
> 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) The
| > | 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
On Mon, Jan 31, 2005 at 09:47:42AM +0200, Jari Aalto said:
> | 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 cou
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 200 # app
Package: clamav-daemon
Version: 0.81-2
Severity: normal
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 200 # appro
10 matches
Mail list logo
