This is the mail archive of the
mailing list for the Cygwin project.
Re: link(2) and atomic file creation on NFS
- To: "Noel L Yap" <yap_noel at jpmorgan dot com>
- Subject: Re: link(2) and atomic file creation on NFS
- From: James Youngman <jay at gnu dot org>
- Date: 29 Aug 2001 22:11:41 +0100
- Cc: cygwin at cygwin dot com
- References: <85256AB7.0071B8B2.email@example.com>
"Noel L Yap" <firstname.lastname@example.org> writes:
> Would a mkdir do the trick?
Ordinarily, yes. (As CVS does, of course).
However, SCCS itself (i.e. the venerable AT&T-as-was product) uses
lock _files_ of the form z.foo. I hesitate before using lock
directories instead, because interoperability is the only (!) priority
of CSSC; I cannot afford to asopt a strategy which may fail to
interoperate completely with SCCS itself.
> I have some existing code which uses link(2) to achieve atomic locking
> on Unix over NFS (since O_EXCL does not work over NFS). The
> application (a GPLed SCCS clone) now compiles under Cygwin, but one
> remaining problem is that the lockfile code uses link(2) to create a
> hard link to an open file.
Manchester, UK. +44 161 226 7339
PGP (GPG) key ID for <email@example.com> is 64A95EE5 (F1B83152).
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html