Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.hawaii.edu!ames!hookup!news.kei.com!newsfeed.internetmci.com!in1.uu.net!zippy.cais.net!cais3.cais.com!leland From: leland@cais3.cais.com (Robert Leland) Newsgroups: comp.unix.bsd.bsdi.misc,comp.mail.elm Subject: Re: elm problems Followup-To: comp.unix.bsd.bsdi.misc,comp.mail.elm Date: 28 Nov 1995 03:54:10 GMT Organization: E Lines: 28 Message-ID: <49e152$689@zippy.cais.net> References: <30B9DFFC.4107@infohwy.com> NNTP-Posting-Host: cais3.cais.com X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:1589 comp.mail.elm:18029 Oliver Soell (oliver@infohwy.com) wrote: : I recently upgraded to version 2.0.1 from 1.1 of BSDI, and elm is : giving me problems. I was using elm under the old version, and when : I moved all my files over to the new version (on a new box as well), : my mail still worked like a charm, but when I add a new user who : wants to use elm, it gets tricky. : When I run elm as a newly created user, it gives a message at the : bottom of the screen saying "Waiting to read mailbox while mail is : being received: attempt #0" and the number of attempts goes up ad : infinitum. I've checked all the permissions on the spool directory, : the spool file itself, and it all seems to be hunky dory. 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 :-)! : Anyone have any idea what this problem might be a product of? : Thanks, and please email directly as well as to the group, : Oliver Soell : Info-Highway International Inc. System Adminstrator : oliver@infohwy.com