AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2021.04.23 13:46 "[Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Pablo Conesa
2021.04.24 14:52 "Re: [Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Bob Friesenhahn
2021.04.24 15:04 "Re: [Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Bob Friesenhahn
2021.04.26 09:43 "Re: [Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Pablo Conesa
2021.04.24 20:00 "Re: [Tiff] Tiff Digest, Vol 29, Issue 10", by Richard Nolde

2021.04.24 15:04 "Re: [Tiff] "TIFFAdvanceDirectory": Error fetching directory count .....getting fewer "frames" but still working..", by Bob Friesenhahn

The rename() system call within the same filesystem is normally expected to be atomic. This still does not mean that two clients of a server can not have a differing opinion of the current state.

Some sort of locking beyond whether a file appears to exist or not is likely to be required.

I should also mention that libtiff and its utilities do not invoke fsync() or fdatasync() to force that the data just "written" is forced to underlying store. This is not done since it can be slow to complete.

If the client is using TIFFClientOpen() then it could arrange to do that.

Bob

Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt