Cami Sardinha wrote: > Tobias J. Kreidl wrote: > >> So, in the case of 5k connections per minute, the server is probably >> saturated... does policyd log that it's reached its limit? >> > > Connections per minute do not mean much. Concurrent connections > is what matters. It should log when its limit has been reached. > > My implication was that the number of connections at times is very high, so one could readily exceed the file descriptor maximum, and hence the limit on the number of concurrent connections.
Frankly, I think you'd have to have a pretty hefty amount of processing to run that many email connections plus policyd plus whatever else might be running on your mail server (amavisd, spamassassin, etc.) to sustain that kind of load. Currently, we have two mail gateways and run spamassassin on a separate cluster of machines, and will likely expand to additional servers. The added advantage is that with enough servers, you can take one down for maintenance or one can fail without generally having a bottleneck in the throughput. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
