[Fwd: Re: Possible bug in kernel 2.2.12 and 2.2.13]

Derek Martin (derek@netria.com)
Tue, 16 Nov 1999 14:09:17 -0500

-------- Original Message --------
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Message-ID: <38306495.7FA263A3@netria.com>
Date: Mon, 15 Nov 1999 14:52:53 -0500
From: Derek Martin <derek@netria.com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Possible bug in kernel 2.2.12 and 2.2.13
References: <38305B9F.639A05DA@netria.com>
<shsiu33wnxs.fsf@charged.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Trond Myklebust wrote:
>
> >>>>> " " == Derek Martin <derek@netria.com> writes:
>
> > svc: svc: lockd: unable to monitor 192.X.X.X
>
> <snip>
> > 1) a locking bug
>
> Not a bug. It's your responsibility to run the 'rpc.statd' daemon if
> you want to use file locking over NFS. This needs to be done on both
> the client and the server.

It was running, as was rpc.quotad, rpc.mountd, and rpc.nfsd. RedHat's
init scripts start these programs automatically at boot time. I may
have some complaints about RedHat, but they generally make sure the
right stuff gets started in their rc scripts.

And I goofed up those messages... the svc messages were supposed to be:

svc: unknown version (3)
svc: unknown program 100227 (me 100003)

I believe these are both pertaining to nfs v3 (nfsd and rpc).

-- 
DM


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/