From owner-freebsd-hackers  Tue Nov 14 11:31:21 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA06113
          for hackers-outgoing; Tue, 14 Nov 1995 11:31:21 -0800
Received: from dtr.com (dtr.rain.com [204.119.8.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA06070
          ; Tue, 14 Nov 1995 11:31:10 -0800
From: bmk@dtr.com
Received: (from bmk@localhost) by dtr.com (8.6.12/8.6.9) id LAA03668; Tue, 14 Nov 1995 11:29:45 -0800
Message-Id: <199511141929.LAA03668@dtr.com>
Subject: Re: elm problem :)
To: roberto@keltia.freenix.fr (Ollivier Robert)
Date: Tue, 14 Nov 1995 11:29:45 -0800 (PST)
Cc: bmk@dtr.com, geoff@ginsu.com, bsd@ee.petra.ac.id, questions@freebsd.org,
        freebsd-hackers@freebsd.org
In-Reply-To: <199511141728.SAA07475@keltia.freenix.fr> from "Ollivier Robert" at Nov 14, 95 06:28:45 pm
Reply-To: bmk@dtr.com
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 523       
Sender: owner-hackers@freebsd.org
Precedence: bulk


> It seems that bmk@dtr.com said:
> > have existed, I don't know).  I've always had to use flock style locking
> > - fcntl always seemed to cause the symptoms the original complaint
> > described.

> I used to compile Elm  setgid mail with all  three types  of lock till  Rod
> said that without the setgid and with both the 755 permissions on /var/mail
> and fcntl locking it was working beatifully. It runs like that since.

Just got an opportunity to recompile and test using only fcntl locking -
and it now works. :)