Jorge, That's seconds.
Jorge Bastos wrote: > Aaron, just one more question, > the: > TIMEOUT=4000 > > this value is in milisecunds? > > > ----- Original Message ----- From: "Aaron Stone" <[EMAIL PROTECTED]> > To: "DBMail mailinglist" <[email protected]> > Sent: Wednesday, December 20, 2006 6:11 PM > Subject: Re: [Dbmail] Timeout's with Outlook 2003 > > >> On Wed, 2006-12-20 at 16:54 +0000, Jorge Bastos wrote: >>> Hi, >>> Guys, I'm having complains about timeouts with outlook 2003. >>> i have about 40/50 connections, mixed IMAP and POP3 (80% POP3, 20% >>> IMAP) at the same time in the work time. >>> Maybe this is some need of a fine tunning to dbmail.conf, any >>> sugestion? >> >> The most obvious configuration items are these below. Values here are >> the defaults, and they are way, way too small for anything but a testing >> installation while you are first figuring out if you'd like to begin >> using DBMail seriously. Also note my comment about making sure that you >> have your database engine configured to handle enough simultaneous open >> connections; you need one per DBMail child process. >> >> A good way to monitor your open connections is to issue this sequence: >> >> kill -USR1 `cat /var/run/dbmail-<daemon>.pid` >> sleep 1 >> cat /var/run/dbmail-<daemon>.state >> >> With a little 'grep' and 'wc' magic, you can count open active (value of >> 1) and inactive but alive (value of 0) never started (value 255) and >> started but reaped (value of -1). (I think I remember those right ;-) >> >> # # Default number of child processes to start. >> # >> NCHILDREN = 2 >> If you know that you're going to have 20-30 each of IMAP and POP3 >> (remember they are a separate pool of daemons!) then spawn the first >> 10-15 right at startup. >> # # Maximum number of child processes allowed. # >> MAXCHILDREN = 10 >> If you might have up to 50 IMAP and/or 50 POP3 all at once, use that as >> your max children value. You'll also need to tune your max database >> connections in your my.cnf or postgresql.conf to be the *sum* of all >> maxchildren values for all daemons that you are launching. >> >> # # Unused children to always have availale. >> # >> MINSPARECHILDREN = 2 >> # # Maximum unused children allowed to be active. >> # >> MAXSPARECHILDREN = 4 >> If you have a lot of users making short connections, checking their >> email and then fully disconnecting, you can use lower maxchildren values >> but you should have higher sparechildren values. This keeps more >> processes waiting around to service incoming connections without waiting >> for process startup time to begin handling a new connection. >> >> If you tend to have, say, 30 connections all day and then 5 all night, >> and not much "flapping", use lower sparechildren values, since they >> aren't going to help you overnight and you can afford the one-time >> morning email login delays (on the order of like 1-2 seconds to fire up >> a new process and database connection; which is a small part of the time >> it takes to download your new email for the day, so it's no big deal). >> >> Hope this helps! >> >> Aaron >> >> _______________________________________________ >> DBmail mailing list >> [email protected] >> https://mailman.fastxs.nl/mailman/listinfo/dbmail >> > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
