From owner-freebsd-stable Thu Jun 22 12:43:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id C615C37BE03 for ; Thu, 22 Jun 2000 12:43:28 -0700 (PDT) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 4AEC1E8D3 for ; Thu, 22 Jun 2000 15:43:24 -0400 (EDT) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id PAA37492; Thu, 22 Jun 2000 15:43:24 -0400 (EDT) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14674.27740.186808.162335@onceler.kcilink.com> Date: Thu, 22 Jun 2000 15:43:24 -0400 (EDT) To: stable@FreeBSD.org Subject: Re: file locking In-Reply-To: <200006221639.JAA06440@freeway.dcfinc.com> References: <200006221639.JAA06440@freeway.dcfinc.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "CRL" == Chad R Larson writes: CRL> Guys, this seems like a bug, or at least a mis-feature, to me. CRL> If a process locks a region of a file using the POSIX-style locks, a CRL> subsequent attempt to use the BSD flock call to lock the whole file CRL> fails. This is arguably a silly thing to do, but still... FWIW, this fails on BSD/OS 4.0.1 as well, so must be a generic BSD issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message