From owner-freebsd-security Wed Aug 9 3: 2:54 2000 Delivered-To: freebsd-security@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 74D5C37B9A3 for ; Wed, 9 Aug 2000 03:02:49 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13MR8S-000Cuo-00; Wed, 09 Aug 2000 09:22:48 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13MR8V-000DC0-00; Wed, 09 Aug 2000 09:22:51 +0100 Date: Wed, 9 Aug 2000 09:22:51 +0100 From: Ben Smithurst To: "Vladimir Mencl, MK, susSED" Cc: FreeBSD-SECURITY Subject: Re: pine 4.21 port issues? Message-ID: <20000809092250.A48327@strontium.scientia.demon.co.uk> References: <20000808201626.I261@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Vladimir Mencl, MK, susSED wrote: > On Tue, 8 Aug 2000, Gerhard Sittig wrote: > >> Question: How does Pine (or C-Client in this scenario) modify >> the mailbox and how does it lock against the MTA delivering into >> the box? >> > > Well, does anybody now, how the locking against the MTA is done? fcntl() or flock() in most cases, I think. Or dotlocking, where to lock $FILE you create $FILE.lock with O_EXCL|O_CREAT so it fails if the lock already exists, but that seems crude really, when fcntl()/flock() are so much easier and probably more efficient and reliable. > How do multiple copies of the MTA lock against each other (e.g., > multiple procmails) ? And how does finally an MUA lock against the MTA ? All the same way. If the file is locked, neither the MTA or the MUA cares or knows what has locked it, they wait until it's unlocked. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message