record locking and portmapper error

[Barry Margolin]

In article <1991May7.234142.15065 at ddtg.com> zhuo at ddtg.com (Victor Zhuo) writes:
>I am recently working on a very simple program and got a strange
>error back from the system. The program opens a disk as a raw device
>then locks a portion (64 bytes) of it (for read) through system call fcntl().
>Somewhere in fcntl(), the system prints out an error message on console
>"Portmapper not responding; still trying"
>and fcntl() never returns back. This disk has nothing to do with inet.

If your system supports a network lock manager, then *all* file locks must
be registered with it, in case a process on another host tries to lock the
same file via a network file protocol.
-- 
Barry Margolin, Thinking Machines Corp.

barmar at think.com
{uunet,harvard}!think!barmar