From owner-freebsd-hackers  Mon Nov 13 15:29:09 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA05761
          for hackers-outgoing; Mon, 13 Nov 1995 15:29:09 -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 PAA05754
          ; Mon, 13 Nov 1995 15:28:56 -0800
From: bmk@dtr.com
Received: (from bmk@localhost) by dtr.com (8.6.12/8.6.9) id PAA07428; Mon, 13 Nov 1995 15:26:12 -0800
Message-Id: <199511132326.PAA07428@dtr.com>
Subject: Re: elm problem :)
To: roberto@keltia.freenix.fr (Ollivier Robert)
Date: Mon, 13 Nov 1995 15:26:12 -0800 (PST)
Cc: geoff@ginsu.com, bsd@ee.petra.ac.id, questions@freebsd.org,
        freebsd-hackers@freebsd.org
In-Reply-To: <199511132209.XAA04336@keltia.freenix.fr> from "Ollivier Robert" at Nov 13, 95 11:09:19 pm
Reply-To: bmk@dtr.com
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 812       
Sender: owner-hackers@freebsd.org
Precedence: bulk


> It seems that User GEOFF said:
> > I found that if I compiled fcntl into elm it wouldn't work.  I had 
> > /var/mail wide open and still couldn't get the locking working.  I had to 
> > remove fcntl for it to work.

> Have you tried the port in /usr/ports/mail/elm ? My  Elm is not the same as
> I try to follow M. Elkins patches (ME8b+ now :-)) but it should work.

I wasn't able to get it working with fcntl locking, either.  I compiled
and installed it long before I knew of the existance of a port (one might
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.

Then again, I'm not exactly a UNIX programming guru - I know enough to
be extremely dangerous. :)

Take it with a (rather large) grain of salt.