*BSD News Article 44743


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!EU.net!Germany.EU.net!zib-berlin.de!news.tu-chemnitz.de!irz401!narcisa.sax.de!not-for-mail
From: j@narcisa.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: elm 2.4 and FreeBSD 2.0
Date: 30 May 1995 17:09:33 +0200
Organization: Private U**x site, Dresden.
Lines: 23
Message-ID: <3qfcfd$dok@bonnie.tcd-dresden.de>
References: <D82tBw.Fzs@ct.covia.com> <D89LGF.93M@luva.lb.bawue.de> <3pi6di$r4m@helios.cto.us.edu.pl>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

>>>/var/mail is
>>>
>>>	 drwxrwxr-x 2 bin bin 
>
>>Set it to 1777
>
>Or recompile Elm with dot - style - locking, without using flock()
>system function. It helped me.

Are you sure you didn't reverse this sentence?  Dot-style-locking
requires write access to the directory.  (Which is considered a
security hole for a certain race condition, hence dot-style-locking is
deprecated unless you really need it [e.g. for a NFS-mounted spool
directory] and don't care for the security issues.)

Either flock() or fcntl() locking should work fine with the default
permissions.  I'm using it all the time this way.

-- 
cheers, J"org                      private:   joerg_wunsch@uriah.heep.sax.de
                                   http://www.sax.de/~joerg/

Never trust an operating system you don't have sources for. ;-)