Hi, I'm the Recoll developper. For some reason, I never got the messages about this problem.
It is clearly a consequence of problem 471976 (excessive memory usage during indexing). Recoll can't exit without flushing the index (this would produce a corrupted database). So the alternative is to either rezero the index and exit immediately, or flush the data and hope it won't take too long. The second approach is more reasonable in most cases. It might be possible to differentiate INT, TERM and QUIT to optionally select the first one, but I doubt many people would bother. This problem is just a secondary effect, which will go away if a fix can be found for Bug#471976. jf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
