Re: oom-killer vs system not reachable

2004-12-19 Thread Henrique de Moraes Holschuh
On Sun, 19 Dec 2004, Robert Ian Smit wrote: > not work with it. There is so much mail that IMAP would be way to > slow. Mutt is very fast once the mailbox is open. Reading and Ha! Trash like uw-imap would be slow. Try it with Cyrus IMAPd 2.1, it is packaged and if you follow the README.Debian.si

Re: oom-killer vs system not reachable

2004-12-19 Thread Sam Watkins
On Sun, Dec 19, 2004 at 10:28:28AM +0100, Robert Ian Smit wrote: > The points concerning the mbox file are taken (in fact I knew as > much). Do you think that Linux might stop to respond or get stuck > for a while as a result of the big file. One problem would be when mutt rewrites the file on ex

Re: oom-killer vs system not reachable

2004-12-19 Thread Robert Ian Smit
* Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [18-12-2004 20:14]: > This is NOT one single 1.5GB mbox file is it? If so, do yourself > a big favour and switch it to maildir. Or store all that mail in > an *indexing* IMAP server Yes it's one single file. It's not my mailbox. Personally I cou

Re: oom-killer vs system not reachable

2004-12-18 Thread Henrique de Moraes Holschuh
On Sun, 19 Dec 2004, Sam Watkins wrote: > > The system is mainly used as a dropbox for a huge amount of mail. > > Mutt is opening and working on a 1.5 GB mbox. Considering this > > usage, should we apply special configuration or should a 'vanilla > > system' be able to cope with this? Mutt might w

Re: oom-killer vs system not reachable

2004-12-18 Thread Sam Watkins
On Sat, Dec 18, 2004 at 10:37:22AM +0100, Robert Ian Smit wrote: > Are those oom problems related to hardware, kernel or userland > software? userland software eating all the virtual memory > The system is mainly used as a dropbox for a huge amount of mail. > Mutt is opening and working on a 1.5

oom-killer vs system not reachable

2004-12-18 Thread Robert Ian Smit
A system connected to a home dsl connection is unreachable from time to time. The ssh session is locked. Starting a new session is not possible. After some time (10 to 30 minutes) it will be possible to log in again. At first I felt it was caused by an unreliable internet connection. During one of