Mitch (WebCob) writes:
Same question I guess applies to other limit conditions... like
MAXDAEMONS,
MAXPERIP etc. Is there a way to detect if the limits are being tested? I
There is a warning message that gets logged when you hit MAXDAEMONS.
No warning messages are logged when you hit MAXPERC or MAXPERIP.
You don't
want your logs quickly filled when someone's trying to throw several
thousand connections at you, per second.
Two ideas... or suggestions...
1) could a "log file" be written or touched to indicate the last time one of
these events occured? That way there would be no danger of spewing to much
crap into the logs... Just a simple timestamp or even a 0 byte file touched
when the event occurs... or perhaps just the address that caused the
error... one record - overwrite as needed.
optionally, if these log messages were available in a debug mode, it might
be a helpful diagnostic tool...
2) could the localhost have a separate set of limits? If not defined,
default to the original - if defined, use them?
I'm not able to do this right now, but would like your thoughts on the
idea - maybe it's an easy change - maybe there is something stupid about the
idea...
More intelligent logging in couriertcpd is certainly a good idea. However,
as far as carving out an exception for localhost goes, I don't see a clean
way to go about doing that.
In case you missed it - in the last month I was pretty busy disecting
everything apart, and putting it back together again. This stuff has to
wait.
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] imap / pop3 maxpe...
