From: Hacksaw <hacksaw@hacksaw.org>
To: kernel@ddx.a2000.nu, linux-kernel@vger.kernel.org
Subject: Re: unexplained high load
Date: Wed, 10 Jan 2001 16:27:28 -0500 [thread overview]
Message-ID: <200101102127.f0ALRSr01062@habitrail.home.fools-errant.com> (raw)
In-Reply-To: Your message of "Wed, 10 Jan 2001 22:06:27 +0100." <Pine.LNX.4.30.0101102203340.4377-100000@ddx.a2000.nu>
>don't think
>w,uptime,top give the same value
The fact that they all give the same value does not indicate that you have not
been cracked. Obviously, part of the hacking is to cover trails; it'd be a
pretty poor job if they reported different values.
The mm stuff from your other message is, I think, an indication that you might
be being hit by a memory management bug that was corrected in 2.2.19pre2.
It is my sincere belief that you will need to upgrade your kernel, but you are
in no serious danger.
If it's a firewall box, you should be running tripwire or some free variation,
to help eliminate the possibility that cracking would go undetected.
-
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:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-01-10 21:47 ` kernel
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
2001-01-10 22:03 ` kernel
2001-01-10 21:57 ` kernel
2001-01-10 22:05 ` Bob Lorenzini
2001-01-10 23:27 Bernd Eckenfels
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=200101102127.f0ALRSr01062@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®