Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!ariel!tesla.unm.edu!sfreed
From: sfreed@tesla.unm.edu (Steve Freed)
Newsgroups: comp.mail.elm
Subject: Re: Save Tagged Mail _Fast_!
Keywords: Kudos
Message-ID: <441@ariel.unm.edu>
Date: 28 Aug 89 21:24:05 GMT
References: <1989Aug23.121938.2967@DRD.Com> <2969@mace.cc.purdue.edu> <1989Aug23.225206.538@DSI.COM>
Sender: news@ariel.unm.edu
Distribution: na
Lines: 17

syd@DSI.COM (Syd Weinstein) writes:
>asd@mace.cc.purdue.edu (Kareth) writes:

>.- Elm be more flexible in file locking.  Our system for instance doesn't have
>.  group id permission set in /usr/spool/mail. 

>File locking needs to be configuration time based, because if it failed,
>you wouldn't want Elm blindly going on, risking loosing the mail.

  This is true, however, it does NOT have to use  both file locking
systems; ie, flock and creating a lock file. It would be great, if in
the Configure if the system has flock, then be asked if they want to
use lock files in addition to. (I'm not sure why one would want to...)


--
Steve.                sfreed@ariel.unm.edu