I'm getting this bug too, only because I have more memory, pstotext gets stuck around page 349 of this stupid manual. It then sits there sucking CPU until killed by hand.
The Right Thing to do is for index++ to limit the number of CPU seconds available to pstotext. (Mine is running for more than 45 CPU *minutes*!). This can be done with the setrlimit system call; exactly how that might be exposed to Ruby is a matter for someone who understands Ruby. But it should be done. I will report in the bug to pstotext. Norman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
