![](https://secure.gravatar.com/avatar/cdac1bce4ec96619cde73d2f2be4e66d.jpg?s=120&d=mm&r=g)
Hartmut Henkel
On Fri, 17 Aug 2007, Taco Hoekwater wrote:
As stopgaps go, this is a pretty decent solution, I think. In general, simply closing the image files after the information discovery and then reopening them for inclusion won't do, as the file may be messed up externally in the time between those two events.
Would it be critical for the image contents, if it has changed in the meantime?
Probably.
Is it needed to nail down the image by keeping the file open?
Actually, this does not help: if another application has the file opened r/w, it can still clobber it while PDFTeX is running. In Posix terms, keeping the file open helps against the effects of creat or unlink, but not against open(..., O_TRUNC).
Are images changing dynamically during a session? Maybe then it might be natural anyway to take the freshest one?
On almost all systems, keeping an open file handle protects you against exactly that.
I don't think so. -- David Kastrup