From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Ion Badulescu <ionut@moisil.cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS 2.4.0-11 noisy messages/NFS rpc.lockd returns error
Date: Mon, 20 Nov 2000 18:11:47 -0700 [thread overview]
Message-ID: <3A19CBD3.FC897005@timpanogas.org> (raw)
In-Reply-To: <200011210111.eAL1Bdj15941@moisil.dev.hydraweb.com>
Ion Badulescu wrote:
>
> On Mon, 20 Nov 2000 17:56:20 -0700, Jeff V. Merkey <jmerkey@timpanogas.org> wrote:
>
> > also, the rpc.lockd program is reporting an error when invoked from the
> > System V init startup scripts:
> >
> > lockd: lockdsvc: invalid argument
>
> lockd is a kernel thread nowadays, remove it from your nfsd start script
> or simply ignore the error (if you want compatibility with 2.2 kernels
> before 2.2.18).
>
Thanks. I saw [lockd] running from ps -ax along with [rpciod] --
performance was also significantly faster. 2.2 compatibility is a
problem, but not a serious one. I am updating initscripts.rpm. More
stuff in the kernel is always better.
Jeff
> Ion
>
> --
> It is better to keep your mouth shut and be thought a fool,
> than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-21 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 0:56 NFS 2.4.0-11 noisy messages/NFS rpc.lockd returns error Jeff V. Merkey
2000-11-21 1:11 ` Ion Badulescu
2000-11-21 1:11 ` Jeff V. Merkey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A19CBD3.FC897005@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox