This is Problems-with-lockf in view mode; [Up]
Date: Sun 26-Sep-1991 09:34:28 From: bpja@codex.oz.au (Brett Adam) Subject: Problems with lockf() I'm having trouble with lockf() under NeXT OS 2.0 Specifically, a call to lockf() of the form lockf(fd, F_TEST, len) where fd is an open file descriptor and len is non-zero fails with errno = EINVAL. The docs say nothing about lockf() returning EINVAL. What's the deal? I get the feeling someone else knows something about this because CAP6.0 which could use lockf() for byte-range locking has been deliberately confgured for NeXT to NOT use lockf(). I'm trying to find a workaround. Please respond via email, even if you post a followup, as our news feeds are somewhat vague.
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.