Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pacbell!pbhyf!rob
From: rob@PacBell.COM (Rob Bernardo)
Newsgroups: comp.mail.elm
Subject: Re: Problem With Network Disconnects And Locks
Message-ID: <5081@pbhyf.PacBell.COM>
Date: 21 Apr 89 04:55:14 GMT
References: <996@itivax.iti.org>
Reply-To: rob@PacBell.COM (Rob Bernardo)
Organization: Pacific * Bell, San Ramon, CA
Lines: 20

In article <996@itivax.iti.org> scs@vax3.iti.org (Steve Simmons) writes:
+I read the locking code for elm, and can see no reason whatsoever to
+have this lock file under BSD.  If it's only for elm, flock() should
+do the job.

Actually some BSD systems use the lock file to lock a mailbox and others
use flock() on the mailbox itself. There was no way for Configure
to determine which type of locking was needed by the particular system,
so what we decided was this:

	1. If the system can do flock(), elm will use it just in case
	it is the way mailboxes get locked on the system.
	2. All systems will lock with a lock file.

This way Configure can't go wrong and the extraneous locks don't hurt.
-- 
Rob Bernardo, Pacific Bell UNIX/C Reusable Code Library
Email:     ...![backbone]!pacbell!pbhyf!rob   OR  rob@pbhyf.PacBell.COM
Office:    (415) 823-2417  Room 4E850O San Ramon Valley Administrative Center
Residence: (415) 827-4301  R Bar JB, Concord, California