> > Comapred to:
> > File has 100 bytes. NFS stats. File gets appended to. NFS reads and returns
> > 200 bytes.
> That's what NFS does, and is what I would expect from a program with
> copy semantics.
So why do you accept different behaviour in the two situations. Why not
argue that NFS should accept the answer from stat or try the read, not do
different things depending on the result?
-- [======================================================================] [ Kevin Lentin Email: K.Lentin@cs.monash.edu.au ] [ finger kevinl@fangorn.cs.monash.edu.au for PGP public key block. ] [ KeyId: 06808EED FingerPrint: 6024308DE1F84314 811B511DBA6FD596 ] [======================================================================]- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu