From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: nfs lockd
Date: Thu, 26 Jul 2001 05:57:50 -0800 [thread overview]
Message-ID: <20010726055750.J19641@plato.local.lan> (raw)
In-Reply-To: <20010726131353.83EABDB9F0@atlas.valhalla.net>; from iain@sandoe.co.uk on Thu, Jul 26, 2001 at 02:14:14PM +0100
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On Thu, Jul 26, 2001 at 02:14:14PM +0100, Iain Sandoe wrote:
>
> the init scripts start-up of lockd has been failing for quite some time on
> my installations (prob. since 2.4.x started).
>
> I believe I'm up-to-date on utils/nfs stuff etc.
>
> is this a known problem - or something wrong with my set-up?
the problem is your initscript, lockd is started automatically by the
kernel. debian's initscript checks whether the userspace lockd
program should be run or not (all that program actually does is tell
the kernel to start the lockd thread if its not already).
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
prev parent reply other threads:[~2001-07-26 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 13:14 nfs lockd Iain Sandoe
2001-07-26 13:57 ` Ethan Benson [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=20010726055750.J19641@plato.local.lan \
--to=erbenson@alaska.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).