Subject: Re: [netatalk-admins] movieplayer and such with afpd
From: wesley.craig@umich.edu
Date: Sun Dec 14 1997 - 13:14:55 EST
Here's the big block comment about the synchronization lock code in
fork.c:
/*
* Perform synchronization locks. There are a couple of ways of
* doing this. The method we're using here, translates W & !R
* to EX, and R & !W to SH. This will allow multiple readers
* and one writer. An alternate method translates R & W to SH,
* and !R & !W to EX. This allows multiple writers, but limits
* the reads to one, which doesn't make much sense, since most
* apps will want to read *and* write.
*
* Note: By doing this, there's pretty much no point in doing
* byte range locking. If you open for writing, you have a lock
* no one else can break.
*
* One last thing: We do the locking late, so we can still return
* data on a "Deny Conflict" error.
*/
:wes
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:28:28 EST