Matt Kettler wrote: > Daniel J McDonald wrote: > >> On Fri, 2007-10-26 at 08:16 -0400, Matt Kettler wrote: >> >> >>> Justin Mason wrote: >>> >>> >>>> What else can we do? >>>> >>>> >>>> >>> Add code to generate a lint warning any time a .cf file over 1mb is read >>> unless a config option is set to silence it? >>> >>> >> But people don't read logs, or they would know... I'd suggest die-ing >> instead. >> > > -1 on die-ing. There's no precedent for that in any of SA's existing > behavior, even under the most severe config errors. This is largely done > because it could screw over someones mail queue following an upgrade. > > And in this case, even if they read the logs, or ran a --lint, they > wouldn't know anything other than "it's slow" and maybe "it eats memory > like a hog". At least this way we can reach the ones that actually check > the basics. > > > >
another example: machine reboots and for some reason, a new big file is there. nobody to read logs. I don't think there is now a need to have a general solution for large files. the problem of the black*.cf can be solved by - rename the file to something like READWARNINGINSIDEFILE-black*.cf - create empty black*.cf there's no reason to punish those who do efforts to listen to advice. those who blindly download files with RDJ or other will notice that their system is faster and that some spam may be missed. not a critical issue.
