Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!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: Lock file
Message-ID: <2795@mace.cc.purdue.edu>
Date: 26 Jul 89 20:23:18 GMT
References: <3941@cps3xx.UUCP> <263@ariel.unm.edu>
Organization: Purdue University Computing Center
Lines: 23

In article <263@ariel.unm.edu> sfreed@tesla.unm.edu (Steve Freed) writes:
>usenet@cps3xx.UUCP (Usenet file owner) writes:

>>I am having problems with ELM not having group access to /usr/mail.
>>It says " Can't create lock file! Need write permission in "/usr/mail/".
>>Can anyone tell me what I need to configure to give ELM group access. 

>You need to have elm set gid (group I.D.) and in the same group as
>/usr/mail with /usr/mail read, write, and executable by group.

That is if you set up your spool directory that way.  Purdue has gone about
leaving it read and executable but not writable by group.  This helps out
security wise.  However, Configure will set Elm up so that it will try and
use all the nice flocking/lock files, nevertheless.  The solution is easy,
just edit leavembox.c, the mk_lockname routine, in the src directory, and
lock.c, lock routine, in the filter directory so that it uses a lock file that
is in the /tmp directory.  I haven't gotten around to fixing the filter part
yet, but I'm pretty sure that's will solve the problem.

I'd like to see Configure ask where it should put lock files instead of just
presuming where it should go based on if the system is Xenix or not.

-kareth.