Robert Banz a écrit :
>> I don't have any system log that complains about something and the
>> only
>> Cyrus message I got is a DB4 warning about lockers. I think the DB4 in
>> question is the TLS sessions cache DB and in my case the number of
>> lockers can be as high as 8 000...
>>
>
> Dum
On Tue, 29 Apr 2008, Eric Déchaux wrote:
Pascal Gienger a écrit :
Eric Déchaux <[EMAIL PROTECTED]> wrote:
The older infrastructure can stand the 42 000 concurrent sessions, the
new one can't : I was expecting each frontend to be able to handle 5 500
concurrent sessions but they are not. Aroun
> Quoting Simon Matter <[EMAIL PROTECTED]>:
>
>>> Hi,
>>>
>>> i tried to compile cyrus 2.3.12p2 on a x86_64 system.
>>>
>>> first i had to replaye config.sub which is shipped with cyrus with a
>>> nerwer version found on my system. This problem already exiss in 2.3.8
>>>
>>> the make stopps with an
Quoting Simon Matter <[EMAIL PROTECTED]>:
Hi,
i tried to compile cyrus 2.3.12p2 on a x86_64 system.
first i had to replaye config.sub which is shipped with cyrus with a
nerwer version found on my system. This problem already exiss in 2.3.8
the make stopps with an error while making perl/imap.
> Hi,
>
> i tried to compile cyrus 2.3.12p2 on a x86_64 system.
>
> first i had to replaye config.sub which is shipped with cyrus with a
> nerwer version found on my system. This problem already exiss in 2.3.8
>
> the make stopps with an error while making perl/imap.
> Can someone confirm this bug?
### Making all in /zdv-system/cyrus-imapd-2.3.12/perl/imap
Checking if your kit is complete...
Looks good
Writing Makefile for Cyrus::IMAP
make[2]: Entering directory `/zdv-system/cyrus-imapd-2.3.12/perl/imap'
cp IMAP/Admin.pm blib/lib/Cyrus/IMAP/Admin.pm
cp IMAP.pm blib/lib/Cyrus/IMAP.pm
cp IMA
Rob Mueller a écrit :
>> On current production platform the frontends use swap massively but the
>> impact is far less than on the new platform.
>>
>
> It's not so much how much swap is actually used, but how much is being paged
> in or paged out at any time. If there are memory pages not bei
Pascal Gienger a écrit :
> Eric Déchaux <[EMAIL PROTECTED]> wrote:
>
>> The older infrastructure can stand the 42 000 concurrent sessions, the
>> new one can't : I was expecting each frontend to be able to handle 5 500
>> concurrent sessions but they are not. Around 3 000 / 3 500 concurrent
>> sess
> On current production platform the frontends use swap massively but the
> impact is far less than on the new platform.
It's not so much how much swap is actually used, but how much is being paged
in or paged out at any time. If there are memory pages not being used at
all, the OS will swap th
Eric Déchaux <[EMAIL PROTECTED]> wrote:
> I would have loved to put Solaris, Zones and Massaging Server here but it
> was not a possibility. Custorme chose was VMware + Linux + Cyrus.
Just as a sidenote:
As closed source is not an option here, we use cyrus imap 2.3.12 on Solaris
and not messagin
10 matches
Mail list logo
