On Freitag 06 Februar 2009 Paul J Stevens wrote:
> Interesting idea. VARCHAR for mysql can be 0x (65535) bytes wide.
> And that is wide enough for me :-) But alas. At least on mysql-5.0
> you can't create a full width index on such wide fields. The index
> only covers the first 255 bytes.
Hm,
In Kmail, I start a search for "Full message" (that's "Vollständige
Nachricht" in german) with content ZMI_FullMessage on an IMAP Folder.
The IMAP command generated is:
104860 UID SEARCH TEXT "ZMI_FullMessage"
And the resulting SELECT is:
SELECT m.message_idnr, v.headervalue, k.messageblk FROM
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=752
==
Reported By:maximP
Assigned To:paul
==
That's hitting a system limit; su to dbmail and run "ulimit -n" to see
the current limit, probably 1024. Then try "ulimit -n 4096" or so
before starting imapd ... or look at where your system sets those limits
(eg. /etc/security/limits.conf on debian) and change it there (setting
is "nofiles" in l
Heh... and on second thought, this is likely due to a filedescriptor
leak, so the below would just be treating the symptom, and only extend
the run-time, not solve it.
On Mon, 2009-02-09 at 09:58 -0700, Jesse Norell wrote:
> That's hitting a system limit; su to dbmail and run "ulimit -n" to see
>
> That's hitting a system limit; su to dbmail and run "ulimit -n" to see
> the current limit, probably 1024. Then try "ulimit -n 4096" or so
> before starting imapd ... or look at where your system sets those
> limits
> (eg. /etc/security/limits.conf on debian) and change it there (setting
> is "n
>
> Heh... and on second thought, this is likely due to a filedescriptor
> leak, so the below would just be treating the symptom, and only extend
> the run-time, not solve it.
>
>
That. There's something not being closed in the tmpfile.
___
Dbmail-de
The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=763
==
Reported By:pixilla
Assigned To:
==
