lkml.org 
[lkml]   [1998]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: size of files in /proc
On Fri, May 22, 1998 at 03:47:57PM +0000, Ton Hospel wrote:
> > I don't get this bit. Why can't there be a race? File gets created, size 0.
> > NFS stats. File gets written to. NFS says no data in file. EOF.
> Valid behaviour. NFS sampled a file property (size), and since it's zero,
> this also implies the file contents (empty).

> > 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

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.149 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site