Article View: comp.sys.next.programmer
Article #648Re: lockf - is it broken
From: Brett Adam
Date: Sun, 12 Apr 1992 04:27
Date: Sun, 12 Apr 1992 04:27
23 lines
1333 bytes
1333 bytes
In article <1992Apr8.153515.3244@n1.nsf.gov> bryan@ad.cise.nsf.gov (Bryan Thompson) writes: > I am trying to port the Faircom ctree+ ISAM package to the next and I am > encountering a problem with lockf() - basically, lockf() persists in claiming > that it is being passed an invalid argument -- frankly it looks like lockf() is > broken. > > So, is lockf() broken? Yes. We went through the same long tirade and finally, NeXT admitted that they had 'disabled' lockf due to potential problems with NFS. Wait until 3.0 - maybe it's fixed - maybe it isn't. BTW. We've built the faircom stuff on the NeXT and it all works well. -- --------------------------------------------------------------- Brett Adam Codex Software Development Pty. Ltd. NeXTMail: bpja@codex.oz.au AppleLink: AUST0335 (Preferred.) (Only if you must)
Technical Details
Message-ID:
<1992Apr12.042751.1595@codex.oz.au>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!mel.dit.csiro.au!yarra!codex!bpjaReferences:
<1992Apr8.153515.3244@n1.nsf.gov>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!mel.dit.csiro.au!yarra!codex!bpja From: bpja@codex.oz.au (Brett Adam) Newsgroups: comp.sys.next.programmer Subject: Re: lockf - is it broken Message-ID: <1992Apr12.042751.1595@codex.oz.au> Date: 12 Apr 92 04:27:51 GMT References: <1992Apr8.153515.3244@n1.nsf.gov> Sender: bpja@codex.oz.au (Brett Adam) Organization: Codex Software Development Pty. Ltd. Lines: 23