From: Hacksaw <hacksaw@hacksaw.org>
To: kernel@ddx.a2000.nu
Cc: linux-kernel@vger.kernel.org
Subject: Re: unexplained high load
Date: Wed, 10 Jan 2001 16:57:12 -0500 [thread overview]
Message-ID: <200101102157.f0ALvCr01485@habitrail.home.fools-errant.com> (raw)
In-Reply-To: Your message of "Wed, 10 Jan 2001 22:49:27 +0100." <Pine.LNX.4.30.0101102247510.4377-100000@ddx.a2000.nu>
> .nfs0000000000ca402500000006
>
> so i think there is some lock from the nfs server or client
>
> will try to restart nfs client
> and see if this fixes it.
>
Most likely you will have to restart the nfs server on the other side as well,
but it's worth a try.
Tripwire watches the checksum of the binaries you deem important, and
complains if they change. There are a few things like it.
See http://freshmeat.net/search/?q=tripwire
-
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/
next prev parent reply other threads:[~2001-01-10 21:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 21:36 Hacksaw
2001-01-10 21:39 ` David S. Miller
2001-01-10 21:52 ` kernel
2001-01-10 21:49 ` kernel
2001-01-10 21:57 ` Hacksaw [this message]
2001-01-10 22:03 ` kernel
2001-01-10 21:57 ` kernel
2001-01-10 22:05 ` Bob Lorenzini
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 23:27 Bernd Eckenfels
2001-01-10 20:34 kernel
2001-01-10 20:58 ` Hacksaw
2001-01-10 21:02 ` kernel
2001-01-10 21:05 ` Doug McNaught
2001-01-10 21:11 ` kernel
2001-01-10 21:06 ` kernel
2001-01-10 21:27 ` Hacksaw
2001-01-10 21:47 ` kernel
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=200101102157.f0ALvCr01485@habitrail.home.fools-errant.com \
--to=hacksaw@hacksaw.org \
--cc=kernel@ddx.a2000.nu \
--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
all inboxes | Powered by JetHome®