Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!purdue!mentor.cc.purdue.edu!mace.cc.purdue.edu!asd
From: asd@mace.cc.purdue.edu (Kareth)
Newsgroups: comp.mail.elm
Subject: Re: Save Tagged Mail _Fast_!
Keywords: Kudos
Message-ID: <3001@mace.cc.purdue.edu>
Date: 28 Aug 89 23:14:08 GMT
References: <1989Aug23.121938.2967@DRD.Com> <2969@mace.cc.purdue.edu> <1989Aug23.225206.538@DSI.COM> <441@ariel.unm.edu>
Distribution: na
Organization: Purdue University Computing Center
Lines: 21

In article <441@ariel.unm.edu> sfreed@tesla.unm.edu (Steve Freed) writes:

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

>>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...)

Well, take for example our system.  It's running Ultrix 2.2 but it
doesn't use the standard group permissions on the mail spool directory.
It HAS to use lock files.  That means I have to manually go in and
change both elm and filter to use lock files.  I'm not sure if all the
other systems on campus use the same method (just reasonably sure).  I
would also like to see Configure ask what method should be used also.

-kareth.