Problems with "rpc.lockd"

Thread View: comp.sys.next.sysadmin

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Eduardo Ostertag Tue, 15 Dec 1992 13:26

#2125

Author: Eduardo Ostertag
Date: Tue, 15 Dec 1992 13:26

22 lines
1374 bytes

Hi there:

I have a NeXTstation (system 3.0) connected to a network with a variety of
UNIX machines (Sun,HP,DG,NCR,etc). The NeXT is our File Server and has two  
SCCI disks (300MB,1GB). After I started getting error messages from  
"rpc.statd" in other UNIX machines, I decided to read the book "Managing  
NFS and NIS" and learned that NFS handles file locking using two daemons:  
rpc.statd and rpc.lockd.

First question: why aren't these daemons being activated from "/etc/rc"?

I decided to activate these daemons after "biod" and the error messages  
from client "rpc.statd" daemons disappeared. Yet, after a day or so (and a  
couple of reboots) I'm having a different problem: "rpc.statd" starts OK,  
but "rpc.lockd" starts but then immediately halts without any error  
messages.

Second question: how can I find out what's wrong with "rpc.lockd"?

Thanks in advance,

-Eduardo Ostertag (ostertag@orden.cl or ostertag@drinkme.cs.umd.edu)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads