Xref: utzoo comp.sources.bugs:989 comp.unix.xenix:2353
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!steinmetz!uunet!milhow1!how
From: how@milhow1.UUCP (Mike Howard)
Newsgroups: comp.sources.bugs,comp.unix.xenix
Subject: Re: Mush 6.2 under SCO Xenix
Keywords: locking(), lockf(), (long)0
Message-ID: <203@milhow1.UUCP>
Date: 28 May 88 21:56:59 GMT
References: <706@jclyde.UUCP> <3679@pasteur.Berkeley.Edu>
Reply-To: how@.UUCP (PUT YOUR NAME HERE)
Organization: Miller/Howard Investments, Malden-on-Hudson, NY
Lines: 17

In article <3679@pasteur.Berkeley.Edu> dheller@cory.Berkeley.EDU.UUCP (Dan Heller) writes:
>In article <706@jclyde.UUCP> root@jclyde.UUCP (The Super User) writes:
>>up (under shell mode) I get a message saying that it can't lock the mail
>>file.  When I try to start up under curses mode I get a segmentation violation
>>and am asked nicely if I want a core dump.  Anybody else having these troubles?
>
>
>	if (Access(filename, W_OK) || lockf(fd, F_TLOCK, 0L)) /* system-v */
                                                     ^^
Make it (char *)0 so that you get the right thing (not that it matters
all that much) for all 286 code models.  I had to do this to make mush6.2
play.

It also core dumped on a segment violation, so I chucked it.
-- 
Mike Howard
uunet!milhow1!how