I get the following error message:

/usr/tmp/htdig8014.pdf: A file write error has occurred.
PDF::parse: cannot open acroread output

I have hundreds of other PDF files on the system and /usr/tmp has over
400MB available.  I assume the PDF file is corrupt, but HOW do I determine
which file is the problem?

The system has two processors and 512MB of RAM.  I don't think the roblem
is with resources.  I do have a few filesystems that are tight on space
though.

Also,  that is the ONLY message I get from rundig.  Does this mean my
indexing failed or succeeded?
 __________________________________________________________________________
| Bryan Swann ([EMAIL PROTECTED])  803/566-0086   803/554-0015 (Fax)          |
| Eagan McAllister Associates, Inc.                                        |
|                                                                          |
|  "Everything must be working perfectly, cause I don't smell any smoke"   |
 --------------------------------------------------------------------------

On Thu, 14 Jan 1999, Matthew Whalen wrote:

> 
> I think I heard David B Swann say:
> >For a single pdf file on my system, I get an error that the parser can not
> >open the acroread output.  However, I can't determine WHICH file is
> >causing the problems.  The document size is set way to high to ba a
> >problem.  How can I easily determine which file is causing the problem?
> 
> I changed a PDF file on my machine a week or two ago and I just noticed
> a couple of days ago that I was getting an error.  I'm not sure if it
> started when I changed PDF file and I didn't notice, or if it's a new error.
> 
> Here's the message:
> 
> Error: Cannot perform calloc
> /var/tmp/htdig2823.pdf: Could not repair file.
> PDF::parse: cannot open acroread output
> PDF::parse: cannot open acroread output
> 
> 
> It's happened the last couple of nights.  I haven't noticed anything about 
> running out of swap space, so I don't really think that it's a memory 
> allocation problem.  Currently, the machine has 511M free swap, which
> is pretty typical.
> 
> Is this the same error that you are getting?
> 
> -matthew
> 
> ----------------------------------------------------------------------
> To unsubscribe from the htdig mailing list, send a message to
> [EMAIL PROTECTED] containing the single word "unsubscribe" in
> the body of the message.
> 

----------------------------------------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the body of the message.

Reply via email to