On Sun, 23 Mar 2008 00:46:27 +0000
Greg Kochanski <[EMAIL PROTECTED]> wrote:
|That's still a bug, even if it is normal. It is incorrect for one program,
|used normally, to disturb the overall operation of the system.
|It's called "denial of service" and it is frowned upon.
I think it can't called 'denial of service'.
|First of all, that was 1.65 (or later 1.9) GB of RAM, not disk space.
|I can afford to devote a few GB of disk space to indices, but keeping it
|all in memory is impractical.
|
|So, if there is a configuration dialog called "Max disk occupation" that
|controls the amount of RAM used, then it is mis-named.
"Max disk occupation" means space in disk, not used RAM. It is not mis-named.
Sorry, if you were confused with it.
|Second, if there *is* a configuration setting to control the use of RAM,
|then you should probably set the default value to 50% of the total RAM on the
|computer. You can obtain the total RAM very easily by reading
|/proc/meminfo on a Linux system. Anything higher than that and your program
|will slow the machine down dramatically.
Unfortunately, there is no configuration for setting up RAM usage for recoll.
|I'll check if I get time to reinstall recoll in the near future.
Please let run 'recollindex' or 'Update Index' from recoll menu one time, it
will take some time/memory/space but after that you can use 'recoll' easily.
IMHO, this can't be call bug. Other indexing programs like beagle also use
similar approaches.
Please CC your reply to [EMAIL PROTECTED]
Thanks!
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Blogs: {ftbfs,kartikm}.wordpress.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
