home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!puc.cl!news
- From: ostertag@orden.cl (Eduardo Ostertag)
- Subject: Problems with "rpc.lockd"
- Message-ID: <1992Dec15.132621.9263@tolten.puc.cl>
- Keywords: nfs, rpc
- Sender: news@tolten.puc.cl (News Manager)
- Nntp-Posting-Host: macha.orden.cl
- Organization: Pontificia Universidad Catolica de Chile
- Date: Tue, 15 Dec 1992 13:26:21 GMT
- Lines: 22
-
- 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)
-