From owner-freebsd-hackers Sun Jun 23 20:37:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id AB8FE37B401 for ; Sun, 23 Jun 2002 20:37:45 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id HAA22591; Mon, 24 Jun 2002 07:38:50 +0400 (MSD) Message-Id: <200206240338.HAA22591@aaz.links.ru> Subject: Re: bug in pw, -STABLE [patch] In-Reply-To: <20020623230923.GM81018@over-yonder.net> from "Matthew D. Fuller" at "Jun 23, 2 06:09:23 pm" To: fullermd@over-yonder.net (Matthew D. Fuller) Date: Mon, 24 Jun 2002 07:38:50 +0400 (MSD) Cc: pherman@frenchfries.net, geoff@sea-incorporated.com, freebsd-hackers@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew D. Fuller writes: ... > > Why use lockfiles, when we can lock files? Let's lock files and > > keep the snack bar open! :-) > > We are locking a file :) > We're just locking one file for the whole subsystem, so the pieces can be > assured of being in sync. Time to implement hierarchic lock. hlock dir lead to fail hlock every file in that dir with ref count == 1 ?? Extremly unefficient -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message