Date: Tue, 24 Aug 1999 17:51:54 -0400 From: Tim Vanderhoek <vanderh@ecf.utoronto.ca> To: Wes Peters <wes@softweyr.com> Cc: Mark Murray <mark@grondar.za>, "Daniel C. Sobral" <dcs@newsguy.com>, Greg Lehey <grog@lemis.com>, Poul-Henning Kamp <phk@critter.freebsd.dk>, Matthew Dillon <dillon@apollo.backplane.com>, FreeBSD Hackers <hackers@FreeBSD.ORG>, FreeBSD Committers <cvs-committers@FreeBSD.ORG>, Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Subject: Re: Mandatory locking? Message-ID: <19990824175154.A8869@ppp18415.on.bellglobal.com> In-Reply-To: <37C2AB77.52678981@softweyr.com>; from Wes Peters on Tue, Aug 24, 1999 at 08:25:59AM -0600 References: <199908232012.WAA78393@gratis.grondar.za> <19990823213857.B99022@ppp18344.on.bellglobal.com> <37C2AB77.52678981@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ). 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. [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. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990824175154.A8869>