Re: NFS Problem in Kernel 2.0.27: inode status not updated

Top Page
Delete this message
Reply to this message
Author: Christoph Lameter
Date:  
To: Piete Brooks
CC: exim-users
Subject: Re: NFS Problem in Kernel 2.0.27: inode status not updated
On Tue, 31 Dec 1996, Piete Brooks wrote:

Piete.Brooks >> We could try to make linux NFS creat() call atomic (Perhaps it already is
Piete.Brooks >> given the need for reliable locks?) resulting in a reliable locking with
Piete.Brooks >> simply creating the lock file.
Piete.Brooks >
Piete.Brooks >Not the way to go ...

With an atomic creat you could reliable locking using a lock file.

Piete.Brooks >
Piete.Brooks >> Linux NFS is currently in the revision process
Piete.Brooks >
Piete.Brooks >Forget it -- not the way to go.

????

Piete.Brooks >
Piete.Brooks >> and there is an experimental lockd available (does not work though ...)
Piete.Brooks >
Piete.Brooks >Yes -- lockd is the way to go.
Piete.Brooks >All systems should have it.

But systems do not have it. With atomic creat a lockd could be simulated
on a user level.

--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5