FYI: Quickly (given this is a quite old bug report)...
I had a similar issue years ago. Turned out that the 'ghostscript' included
a PostScript file called 'loop.ps'. The PS indexer would run ghostscript
on the file to attempt to generate a text output to index. However,
'loop.ps' by its very name, sends the PS interpreter into a loop,
thus the indexer would never complete.
The 'recoll' author was going to address that with timeout kills on
the indexer child to keep it from consuming resources. I'm pretty sure
that happened.
And to the original poster:
ps -awwl -s ${pid-of-offending-process}
and possible 'lsof' output would be helpful.
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.2869 - [email protected] - http://www.ral.ucar.edu/~sdowdy/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
