Bernard Johnson wrote:
> I (and other people I know) have been using VersaMail on a Treo with
> dbmail. For the past year (on different versions of VersaMail and
> different versions of dbmail), things have worked great.
>
> Then, a few weeks ago, when trying to synchronize with the IMAP server,
Sure, that would certainly be a good way to make the information available
across clustered DBMails so that we have the information handy in order to
prevent one user / ip from storming the cluster.
I want to slowly build out the information we have available now, along
the stable series, so that
What about memcache for this type of stuff? I know it mean it'll be in
2.3, not 2.2, but that may be an appropriate cost/benefit decision.
On Fri, 2007-04-06 at 09:34 -0700, Aaron Stone wrote:
>
> > - total number of concurrent connections opened (so we can limit the
> number of
> > connection
On Fri, Apr 6, 2007, Eugene Prokopiev <[EMAIL PROTECTED]> said:
Updated acinclude.m4, will require an autoreconf -f -i from SVN.
>>>
>>>When autoreconf will be executed?
>>
>>
>> You're welcome to run this in your own checkout directory. For SVN, Paul
>> commits these updates. I use Gentoo,
Updated acinclude.m4, will require an autoreconf -f -i from SVN.
When autoreconf will be executed?
You're welcome to run this in your own checkout directory. For SVN, Paul
commits these updates. I use Gentoo, and it puts some weird stuff into
aclocal.m4 that breaks on other distributions.
I
On Fri, 2007-04-06 at 15:26 +0200, Paul J Stevens wrote:
> Aaron Stone wrote:
> > In pool.h, we have this definition:
> >
> > typedef struct {
> > pid_t pid;
> > time_t ctime;
> > unsigned char status;
> > unsigned long count;
> > char * client;
> > } child_
Aaron Stone wrote:
> In pool.h, we have this definition:
>
> typedef struct {
> pid_t pid;
> time_t ctime;
> unsigned char status;
> unsigned long count;
> char * client;
> } child_state_t;
>
> These are the structures that fill up the shared memory segment
On Thu, 2007-04-05 at 12:26 +1000, Boey Maun Suang wrote:
> > Do you get the same set of errors repeated for export.c and
> > sievecmd.c?
>
> I get them for sievecmd.c, but, oddly, not for export.c.
This should now be fixed in SVN. Thanks again for the report!
Aaron
_
