On Mon, Jan 07, 2008 at 03:59:18PM +0000, Adrian Howard wrote: > Actually, I've had some nasty bugs in the past with prints failing > with dodgy NFS mounts. Caused some important data to go away. Not my > code fortunately :-)
In these circumstances print failed but the close on the file did not? I know that it happens the other way, because I clearly remember that a certain firm's compiler got caught with its pants down when a certain firm's NFS implementation went multithreaded in release 2.4 of the OS. With 2.4 write failures (here caused by hitting quotas) were not reported as errors on the writes, but instead only spotted at close time (when everything resynchronised). The compiler wasn't checking the return value of close. Then again, close time might be too late for the application you're describing, if it is holding files open for long periods. Nicholas Clark
