On Wed, 2002-08-07 at 20:24, Gregory Giguashvili wrote:
> I understand that locking file flushes NFS cache, isn't it? Why can't it be
> flushed by O_SYNC and "sync" options presence? This would make the life much
> easier for programmers...
> This means that we will never be able to drop lockd locking and at the same
> time achieve file consistency via NFS?
Welcome to NFS. You basically need file locking (lockf/posix - flock is
not portably applicable to NFS) and you may need to turn off attribute
caching to make O_APPEND work portably.
Its a pain, but NFS has no other way to infer your transaction
constraints. You need to lock for read and for write on all clients, a
client reading without locking may get stale data.
Personally I use my own little daemons to manage transactional data,
ones that understand my transaction rules
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:37 EST