LuKreme:
> On 8-May-2009, at 10:31, Wietse Venema wrote:
> > Short reply: s/mysql/proxy:mysql/
>
> Is there any reason to *NOT* do this? I mean, should you use proxy:
> every time you use a mysql lookup?
It adds latency. This is not a problem for high-concurrency services
such as smtpd. It is
On Sat, May 09, 2009 at 10:20:02AM -0600, LuKreme wrote:
> On 8-May-2009, at 10:31, Wietse Venema wrote:
>> Short reply: s/mysql/proxy:mysql/
>
> Is there any reason to *NOT* do this? I mean, should you use proxy: every
> time you use a mysql lookup?
Sophisticated users who know which tables ar
On Sat, 09 May 2009, LuKreme wrote:
> On 8-May-2009, at 10:31, Wietse Venema wrote:
>> Short reply: s/mysql/proxy:mysql/
>
> Is there any reason to *NOT* do this? I mean, should you use proxy:
> every time you use a mysql lookup?
You do not have to use the proxymap(8) service if your server is
On 8-May-2009, at 10:31, Wietse Venema wrote:
Short reply: s/mysql/proxy:mysql/
Is there any reason to *NOT* do this? I mean, should you use proxy:
every time you use a mysql lookup?
--
Si Hoc Legere Scis Nimium Eruditionis Habes
On May 8, 2009 10:31:37 am Wietse Venema wrote:
> Ray:
> > Hello,
> >
> > System is FreeBSD 7.0, postfix 2.6.2, mysql storage of user info,
> > amvisd-new, and dovecot for authentication and pop/imap. postconf -n at
> > end of post.
> >
> > Just Yesterday I started receiving a lot of
> > "warning:
Ray:
> Hello,
>
> System is FreeBSD 7.0, postfix 2.6.2, mysql storage of user info, amvisd-new,
> and dovecot for authentication and pop/imap. postconf -n at end of post.
>
> Just Yesterday I started receiving a lot of
> "warning: connect to mysql server localhost: Too many connections"
> (Samp
