[576] in Release_7.7_team
Re: Notes for 5/23
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Jun 5 10:55:25 1996
To: Mike Barker <mbarker@MIT.EDU>
Cc: release-team@MIT.EDU
In-Reply-To: Your message of "Wed, 05 Jun 1996 10:50:16 EDT."
<199606051450.KAA05851@megara.MIT.EDU.MIT.EDU>
Date: Wed, 05 Jun 1996 10:55:16 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> 1.13 discuss server not setting acls - ghudson corrected. Problem
> with locking directory, changed to lock only acl file.
Just to make sure there's not a misconception here: the locks used by
discuss are advisory locks; they only cause a process to wait when two
processes try to lock the same thing. By changing discuss to lock the
acl file instead of the meeting directory during acl change
operations, I didn't in any way narrow the scope of the lock.
"changed to lock only acl file" is deceptive; it implies that the old
code somehow prevented any operation within the meeting directory. It
didn't.