Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!mailrus!ames!sun-barr!newstop!texsun!texbell!nuchat!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.mail.elm Subject: Re: Mail to/from a BBS (one login, many users) Message-ID: Date: 4 Jul 90 11:27:25 GMT References: <1990Jun29.074034.12656@actrix.co.nz> <923@limbo.Intuitive.Com> <2690E240.1006@tct.uucp> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 13 In article <2690E240.1006@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes: > Locking issues could be addressed by using Deliver and Elm, both of > which are capable of using the Xenix "/tmp/username.mlk" locking > convention. That's a win because it doesn't break under long user > names -- the temp file is generated with sprintf("/tmp/%.10s.mlk", > basename)'. It's a lose on a network, because different systems have different ideas of what "/tmp" is. I've been working on that problem, and also on the problem of dealing with UNIX $MAIL.lock and Xenix /tmp/$LOGNAME.mlk on the same net. When I have the stuff coded, I'll post. In any case... if you're on a network, stick to $MAIL.lock. -- Peter da Silva. `-_-' +1 713 274 5180.