| To: | qmail-ldap@qmail-ldap.org |
|---|---|
| Subject: | Re: concurrency values |
| From: | Sebastian Benoit <benoit-lists@fb12.de> |
| Date: | Thu, 3 May 2007 12:38:20 +0200 |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | qmail-ldap-list@securepoint.com |
| Delivered-to: | mailing list qmail-ldap@qmail-ldap.org |
| In-reply-to: | <46391622.60200@fct.unl.pt> |
| Mail-followup-to: | qmail-ldap@qmail-ldap.org |
| Mailing-list: | contact qmail-ldap-help@qmail-ldap.org; run by ezmlm |
| Organisation: | Organisation against the bulletization of popular thought as a result of the increasing prevalence of Microsoft PowerPoint(TM) |
| References: | <46391622.60200@fct.unl.pt> |
| User-agent: | Mutt/1.4.2.2i |
Hugo Monteiro(hugo.monteiro@fct.unl.pt) on 2007.05.02 23:52:18 +0000: > Hello all, > > I was wondering if there is any "right thumb" rule for the > incoming/local/remote concurrency values in a clustered qmail-ldap that depends on your setup: incoming concurrency is to protect your server from to many connections, and how many are possible depends on your processing (think spam/virus scanner...) similar logic applies to local & outgoing... /B. -- Sebastian Benoit <benoit-lists@fb12.de> Der Kurs "Flirten für Informatiker" wurde inzwischen zusammen mit "Freeclimbing für Epileptiker" aus allen VHS-Programmen entfernt. [Jochen Lillich in de.alt.sysadmin.recovery]
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | "~control/queuelifetime" for qmail-ldap server., sato x |
|---|---|
| Next by Date: | Re: concurrency values, Hugo Monteiro |
| Previous by Thread: | concurrency values, Hugo Monteiro |
| Next by Thread: | Re: concurrency values, Hugo Monteiro |
| Indexes: | [Date] [Thread] [Top] [All Lists] |