From owner-freebsd-hackers Sun Aug 22 17:23:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2BD1914C23; Sun, 22 Aug 1999 17:23:42 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA15309; Mon, 23 Aug 1999 09:53:15 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA83326; Mon, 23 Aug 1999 09:53:11 +0930 (CST) Date: Mon, 23 Aug 1999 09:53:10 +0930 From: Greg Lehey To: FreeBSD Hackers , FreeBSD Committers Subject: Mandatory locking? Message-ID: <19990823095310.A83273@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just found a need for mandatory locking in Vinum, and I'm wondering how to implement it. If I understand things correctly, our fcntl locking doesn't perform mandatory locking, though System V does if you set the file permissions appropriately. Questions: 1. Do we have some form of mandatory locking? If so, what is it? 2. Would it make sense to implement System V's fcntl semantics? They're rather tacky: you set the setgid bit and reset the group exec bit of the file permissions. 3. Alternatively (or additionally), would it make sense to have an additional fcntl function which performs mandatory locking? I think that it's probably a good idea to implement (3), and also to do (2), possibly subject to a sysctl knob. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message