zhuo@ddtg.com (Victor Zhuo) (05/08/91)
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.
I don't think I have any other process that is using the disk,
but I am not 100% sure. Could anyone tell me what the problem might be or
where I can get more information?
I am using A/UX but I don't think it makes any difference.
--
^ ^ Victor Zhuo
Thank you! V DuPont Design Technologies Group
Z Email: zhuo%ddtisvr@uunet.uu.netbarmar@think.com (Barry Margolin) (05/08/91)
In article <1991May7.234142.15065@ddtg.com> zhuo@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@think.com {uunet,harvard}!think!barmar