Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!yarrina.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!gatech2!swrinde!news.uh.edu!lurch.sccsi.com!news.sccsi.com!usenet From: Oliver Soell <oliver@infohwy.com> Newsgroups: comp.unix.bsd.bsdi.misc,comp.mail.elm Subject: Re: elm problems Date: Wed, 29 Nov 1995 10:26:05 -0600 Organization: Info-Highway International, Inc. Lines: 15 Message-ID: <30BC899D.1A6B@infohwy.com> References: <30B9DFFC.4107@infohwy.com> <49e152$689@zippy.cais.net> Reply-To: oliver@infohwy.com NNTP-Posting-Host: guinness.infohwy.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b2 (Macintosh; I; 68K) To: Robert Leland <leland@cais3.cais.com> Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:1608 comp.mail.elm:18052 >Elm was probably compiled with SYSV file locking. I noticed that on a >BSDI machine, (NetBSD also), that root doesn't experience the problem >but a lowely user does. Soultion would to rebuild elm, when being >configured elm will ask you do you want to use three different types >of locking answer yes to the first two, (uucp and flock() ??) and no >to the third type SYSV locking whatever that is :-)! The thing is that I just installed the elm that was included on the 2.0 CD in /usr/contrib.. I doubt they'd let that go through with an error like that, and I'm sure others are using it just fine.. We shall see. -o