From owner-freebsd-hackers Tue Aug 24 23:18:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 2424B14C81; Tue, 24 Aug 1999 23:18:44 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #1) id 11JWLH-0004qt-00; Wed, 25 Aug 1999 00:15:27 -0600 Message-ID: <37C389FC.3B3237CF@softweyr.com> Date: Wed, 25 Aug 1999 00:15:24 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Tim Vanderhoek Cc: Mark Murray , "Daniel C. Sobral" , Greg Lehey , Poul-Henning Kamp , Matthew Dillon , FreeBSD Hackers , FreeBSD Committers , Garrett Wollman Subject: Re: Mandatory locking? References: <199908232012.WAA78393@gratis.grondar.za> <19990823213857.B99022@ppp18344.on.bellglobal.com> <37C2AB77.52678981@softweyr.com> <19990824175154.A8869@ppp18415.on.bellglobal.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Vanderhoek wrote: > > On Tue, Aug 24, 1999 at 08:25:59AM -0600, Wes Peters wrote: > > > > > > I don't like restricting the breaking of mandatory locks to the > > > superuser. It could be restricted to specific users (say file owner + > > > root)... > > > > How 'bout "anyone who can kill the process holding the lock?" > > + file owner ( + root ). Which processes can't root kill? > Otherwise I would be able to lock ~wes/FreeBSDmarkers and you wouldn't > be able to do anything about it until either notifying me or notifying > root about the process I accidentally left hanging. Hey, I'm the one who gave you write access to it. If I didn't want you write-locking it, I wouldn't give you write access, now wood eye? > [Not that I'm likely to ever need more than an advisory lock on that > particular file, but the principle... :-] > > Hm. ``chmod go-"MayLock" ~wes/Fre*'' The sticky bit could be used. Or better yet, implement file ACLs so I can grant read/write to everyone BUT you. Of course, I can do that now by creating goup "nothoek" right? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message