jdow wrote:
> From: "Matt Kettler" <[EMAIL PROTECTED]>
> Sent: Friday, 2007, October 26 20:19
>
>> I dono, I think that having some --lint warnings generated when the
>> overall config is really absurdly large seems useful for this kind of
>> problem in general. A basic "um, dude, that's a lot of config, are you
>> sure your server can handle this" might be a good thing. You never know
>> when someone else might make a sa-blacklist, or some tool that
>> auto-generates rules might get popular and get out-of-control
>> sometimes.. etc..
>>
>> However, the whole idea of having it kill SA is way out-of-bounds, IMHO.
>> SA won't even do that if you feed it a conf file full of output from
>> /dev/random...
>
> The problem there, Matt, is that the definition of absurdly large varies
> greatly with application.
>
True, which is why I wanted the warning level to be a configurable
option. That way folks can see the warning, decide if there machine is
big enough, and silence the warning if desired.
