--- Paul J Stevens <[EMAIL PROTECTED]> wrote:
> Kevin Baker wrote:
> > --- Paul J Stevens <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Kevin,
> >>
> >>what errors do you see?
> >
> > I was getting the socket error:
> >
> > [error]
> > dbmysql.c,db_connect: MySQL host is set to localhost,
> but
> >
Kevin Baker wrote:
> --- Paul J Stevens <[EMAIL PROTECTED]> wrote:
>
>
>>Kevin,
>>
>>what errors do you see?
>
> I was getting the socket error:
>
> [error]
> dbmysql.c,db_connect: MySQL host is set to localhost, but
> no mysql_socket has been set. Use sqlsocket=... in
> dbmail.conf. Connecting
--- Paul J Stevens <[EMAIL PROTECTED]> wrote:
> Kevin,
>
> what errors do you see?
I was getting the socket error:
[error]
dbmysql.c,db_connect: MySQL host is set to localhost, but
no mysql_socket has been set. Use sqlsocket=... in
dbmail.conf. Connecting will be attempted using the default
sock
Wonderful, thank you Paul, and not just for this, but for all the great
work you are doing on DBMail.
Matt
Paul J Stevens wrote:
I ran into it myself recently, and concluded that there's a bug in the
pool code which doesn't cleanup when a fork fails.
basically what happens is that after fork
I ran into it myself recently, and concluded that there's a bug in the
pool code which doesn't cleanup when a fork fails.
basically what happens is that after forking, a child process tries to
register in the scoreboard. This will fail if there are too many
children. However, upon failure to regis
Could you expound on that? I have seen the same problem, DBMail 2.0.9,
Fedora Core 2, PostgreSQL database backend. One thing I think I noticed
is that the problem happened more frequently when I set IMAPs NCHILDREN
to a small number like 5, that caused a lot of problems, I bumped it
back to 3
This is a known issue that is not 2.0.10 specific.
[EMAIL PROTECTED] wrote:
> Dev-monsters,
>
> Not reproducible on demand so I really can't call/submit it as a bug but
> it's serious enough to post to the dev list in case others are having
> this problem.
>
> Approximately 2 days after upgradin
Kevin,
what errors do you see?
Kevin Baker wrote:
> Thanks Paul,
>
> So I am having trouble installing this.
>
> 1) I removed the previous version of dbmail:
>apt-get remove dbmail*
>
> 2) Set the apt/source.list to unstable version:
>deb http://debian.nfgd.net/debian unstable main
>
Dev-monsters,
Not reproducible on demand so I really can't call/submit it as a bug but
it's serious enough to post to the dev list in case others are having
this problem.
Approximately 2 days after upgrading from 2.0.9/8 (forgot which one) to
2.0.10, my mail server for whatever reason had ov
