Path: utzoo!yunexus!ists!mike
From: mike@ists (Mike Clarkson)
Newsgroups: comp.emacs
Subject: Re: using $HOME/RMAIL.lock as the movemail lock file
Message-ID: <135@ists>
Date: 28 May 88 07:14:11 GMT
Article-I.D.: ists.135
Posted: Sat May 28 03:14:11 1988
References: <11767@duke.cs.duke.edu>
Organization: Institute for Space and Terrestrial Science
Lines: 24

In article <11767@duke.cs.duke.edu>, jwt@tupelo.cs.duke.edu (Jeffrey W. Tannehill) writes:
> 	When using rmail in gnuemacs v18.51, movemail either uses flock
> or it creates a lock file /usr/spool/mail/$USER.lock.  In order to do the 
> latter it has been suggested that movemail be setuid or that it be setgid and 
> /usr/spool/mail be group writeable.  I would like to avoid flock because
> /usr/spool/mail is remotely mounted (via NFS) on some machines, and for 
> reasons of paranoia I would like to avoid a set[ug]id movemail altogether.

How paranoid do you have to be of movemail sgid (2755) daemon, and
/usr/spool/mail group writeable (775)?  Do people see problems with this?




> 	Has anyone considered having movemail create a lock file in
> $HOME/RMAIL.lock instead of in /usr/spool/mail/$USER.lock?  Are there any 
> reasons why this shouldn't be done?

It won't work unless you can get /bin/mail to write lock files there too.
-- 
Mike Clarkson					mike@ists.UUCP
Institute for Space and Terrestrial Science	mike@ists.yorku.ca
York University, North York, Ontario,		uunet!mnetor!yunexus!ists!mike
CANADA M3J 1P3					+1 (416) 736-5611