Paul J Stevens wrote:
Until then, you can either disable IDLE by tweaking the capability
string, or lessen it's impact by tuning the idle_timeout config key.
Got it.
I'd recommend alerting users of this issue in the config file or
elsewhere, as 30 seconds is the default after all. Or disabling IDLE by
default with a CAUTION notice about enabling it and alerting about this
issue.
As with my measly ~25 users this caused network traffic to jump WAY up
and the server to force to a crawl I'd really consider warning users of
2.2 series about using IDLE.
Regards,
--
Aleksander Kamenik
system administrator
+372 6659 649
[EMAIL PROTECTED]
Krediidiinfo AS
http://www.krediidiinfo.ee/
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
