Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com To: "Noel L Yap" Cc: cygwin@cygwin.com Subject: Re: link(2) and atomic file creation on NFS References: <85256AB7.0071B8B2.00@nyc-ntgw-n01.ny.jpmorgan.com> From: James Youngman Date: 29 Aug 2001 22:11:41 +0100 In-Reply-To: <85256AB7.0071B8B2.00@nyc-ntgw-n01.ny.jpmorgan.com> Message-ID: Lines: 28 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii "Noel L Yap" writes: > Would a mkdir do the trick? > > Noel 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. [snip] -- James Youngman Manchester, UK. +44 161 226 7339 PGP (GPG) key ID for is 64A95EE5 (F1B83152). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/