Date: Wed, 9 Aug 2000 09:22:51 +0100 From: Ben Smithurst <ben@FreeBSD.org> To: "Vladimir Mencl, MK, susSED" <mencl@nenya.ms.mff.cuni.cz> Cc: FreeBSD-SECURITY <freebsd-security@FreeBSD.ORG> Subject: Re: pine 4.21 port issues? Message-ID: <20000809092250.A48327@strontium.scientia.demon.co.uk> In-Reply-To: <Pine.GSO.4.10.10008090908070.4913-100000@nenya.ms.mff.cuni.cz> References: <20000808201626.I261@speedy.gsinet> <Pine.GSO.4.10.10008090908070.4913-100000@nenya.ms.mff.cuni.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000809092250.A48327>