Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!jfc
From: jfc@athena.mit.edu (John F Carr)
Newsgroups: comp.unix.wizards
Subject: Re: Why is there an exclusive lock *count* ???
Message-ID: <9036@bloom-beacon.MIT.EDU>
Date: 1 Feb 89 00:23:56 GMT
References: <3775@ttidca.TTI.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: jfc@athena.mit.edu (John F Carr)
Organization: Massachusetts Institute of Technology
Lines: 13

In article <3775@ttidca.TTI.COM> mb@ttidca.tti.com (Michael Bloom) writes:
>Why bother to do this? Isn't the IEXLOCK flag bit sufficient since there
>can only be one exclusive lock at any one time? 

If a process forks while holding an exclusive lock, the number of locks
increases by one (the lock remains until both parent and child have
released it).

--
   John Carr             "When they turn the pages of history,
   jfc@Athena.mit.edu     When these days have passed long ago,
   bloom-beacon!          Will they read of us with sadness
   athena.mit.edu!jfc     For the seeds that we let grow?"  --Neil Peart