From: jan <jan.van.nunen@pandora.be>
To: Hans-Christian Armingeon <linux.johnny@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: knfsd not working in 2.4.18-rc4
Date: Mon, 25 Feb 2002 18:15:31 +0100 [thread overview]
Message-ID: <20020225181531.A2069@abulafia> (raw)
In-Reply-To: <16fLiV-0OqAvgC@fmrl03.sul.t-online.com>
In-Reply-To: <16fLiV-0OqAvgC@fmrl03.sul.t-online.com>
On Mon, Feb 25, 2002 at 04:05:26PM +0100, Hans-Christian Armingeon wrote:
> Hi folks,
> kernel nfsd in 2.4.18-rc4 isn't working when started via the distribution's boot scripts, and I don't know, how to set it up manually. I don't blame the distro's script, but it is a SuSE 7.3.
> I think, it is a kernel issue.
> 2.4.17 worked, 2.4.18-rc4 was the first, who showed this misbehaviour.
> Maybe, it is final relevant?
Hi, well at my place the kernel nfsd is fine (2.4.18-rc4) and has been
for years now actually. I haven't heard of any of such problems with it,
so if I was you I would have a look at your init.d script.
Jan
prev parent reply other threads:[~2002-02-25 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 15:05 knfsd not working in 2.4.18-rc4 Hans-Christian Armingeon
2002-02-25 17:15 ` jan [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=20020225181531.A2069@abulafia \
--to=jan.van.nunen@pandora.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.johnny@gmx.net \
/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