Hi.
The following error message seem to be at warn (syslog priority) or
above:
Oct 30 14:24:57 myhost imapd[12489]: idle for too long, closing connection
Shouldn't this be only an info, or is it really a warning that something
is about to go wrong (which how I think of warnings)?
The other
On 30 Oct 2002, Erik Enge wrote:
The following error message seem to be at warn (syslog priority) or
above:
Oct 30 14:24:57 myhost imapd[12489]: idle for too long, closing connection
Shouldn't this be only an info, or is it really a warning that something
is about to go wrong (which how
On 30 Oct 2002, Erik Enge wrote:
Rob Siemborski [EMAIL PROTECTED] writes:
It could probably go to LOG_INFO.
Is this a configuration option I can adujust? Or can I recompile Cyrus
to use info instead?
It's in imap/imapd.c, near the top of cmdloop().
If you're using Berkeley DB 4
Rob Siemborski [EMAIL PROTECTED] writes:
It could probably go to LOG_INFO.
Is this a configuration option I can adujust? Or can I recompile Cyrus
to use info instead?
If you're using Berkeley DB 4 there's a bug in the locker counting
code that causes this number to not be decremented, so
Rob Siemborski [EMAIL PROTECTED] writes:
It's in imap/imapd.c, near the top of cmdloop().
Will this be fixed in the next release?
Keep in mind that this won't make them entirely go away, since
Berkeley is still the prefered database for duplicate.db and
tls_cache.db. And they *are* a
On 30 Oct 2002, Erik Enge wrote:
I'm not sure I understand. Does that mean I cannot use
--with-duplicate-db and --with-tls-db as skiplist? Will Berkley DB
still be used?
You can, it's just not a great idea performance-wise (skiplist is more
optimized towards enumeration operatons than
On 30 Oct 2002, Erik Enge wrote:
You can, it's just not a great idea performance-wise (skiplist is more
optimized towards enumeration operatons than random access).
Keeping in mind that I will have about 50 users that access their
mailboxes all day, would I notice any performance impact of
Rob Siemborski [EMAIL PROTECTED] writes:
You can, it's just not a great idea performance-wise (skiplist is more
optimized towards enumeration operatons than random access).
Keeping in mind that I will have about 50 users that access their
mailboxes all day, would I notice any performance
Rob Siemborski [EMAIL PROTECTED] writes:
That depends on a number of things. mailboxes.db should be skiplist
for performance reasons anyway.
What is skiplist? Is the code included in Cyrus?
Thanks,
Erik.
On 30 Oct 2002, Erik Enge wrote:
Rob Siemborski [EMAIL PROTECTED] writes:
That depends on a number of things. mailboxes.db should be skiplist
for performance reasons anyway.
What is skiplist? Is the code included in Cyrus?
It's a database format that we wrote to do fast enumarations,
10 matches
Mail list logo
