Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!agate!bionet!csd4.milw.wisc.edu!mailrus!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: process sync - can it be portable?
Keywords: lock
Message-ID: <9461@smoke.BRL.MIL>
Date: 20 Jan 89 19:58:28 GMT
References: <12992@steinmetz.ge.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <12992@steinmetz.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes:
>I have a program which will eventually run a number of copies all
>sharing a number of files. My problem comes with locking...
>The problem is that I want this to be portable.

The general approach to such requirements is to define one's own portable
interface to a necessarily system-dependent implementation of the facility.

The BRL CAD package defines a "resource" structure and a set of macros/
functions for acquiring/releasing resources.  Something of the sort is
probably your best bet.