Help with file locking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Apr 17, 2002 at 03:00:00PM -0700, Mike Fedyk wrote:
> On Wed, Apr 17, 2002 at 02:29:56PM -0700, Andrew Morton wrote:
> > include/linux/fcntl.h:
> > 
> > #define DN_ACCESS       0x00000001      /* File accessed */
> > #define DN_MODIFY       0x00000002      /* File modified */
> > #define DN_CREATE       0x00000004      /* File created */
> > #define DN_DELETE       0x00000008      /* File removed */
> > #define DN_RENAME       0x00000010      /* File renamed */
> > #define DN_ATTRIB       0x00000020      /* File changed attibutes */
> > 
> > It would probably be a simple exercise to add "DN_CLOSE",
> > and then run around and implement it.
> > 
> > (That being said, what was wrong with polling `lsof'
> > output for the absence of the file?)
> 
> root privilege requirements maybe?

That's one, yes.  But DN_CLOSE has other problems too for the initial
scenario --- for example, in NFS (on the server side) there simply
isn't any open or close.  The client simply stops sending more writes;
and a close() doesn't necessarily imply that there is new data
(although it would make sense to restrict DN_CLOSE to close of a
writable fd, which would _usually_ mean the data had been modified.)

--Stephen





[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux