From: David Ford <david@erisksecurity.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: WANTED: Re: VM lockup with 2.4.8 / 2.4.8pre8
Date: Wed, 15 Aug 2001 16:51:34 -0400 [thread overview]
Message-ID: <3B7AE0D6.2090804@erisksecurity.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10108131229270.27903-100000@press-gopher.uchicago.edu> <Pine.LNX.4.33L.0108131451470.6118-100000@imladris.rielhome.conectiva> <20010814220545.D31070@pasky.ji.cz> <Pine.LNX.4.33L.0108131451470.6118-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Mon, Aug 13, 2001 at 02:55:42PM -0300 <9lc0ek$l5k$1@ns1.clouddancer.com> <20010815193521.4DDE8783F5@mail.clouddancer.com>
Also consider that many places use randomized pids. You can only assume
a few things about pids and that has to be done by evaluating kernel
threads and the init pid.
David
Colonel wrote:
>>I also propose to half badness of processes with pid < 1000 - those
>>processes are usually also important, because they are called during
>>boot-time and they usually handle important system affairs.
>>
>
>The belief that boot started processes remain under a pid < 1000 is
>flawed. Simple example: the postfix mail server.
>
next prev parent reply other threads:[~2001-08-15 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 17:47 VM lockup with 2.4.8 / 2.4.8pre8 Roy C. Bixler
2001-08-13 17:55 ` WANTED: " Rik van Riel
2001-08-14 19:04 ` Jon 'tex' Boone
2001-08-14 19:32 ` Rik van Riel
2001-08-14 20:05 ` Petr Baudis
2001-08-14 20:27 ` Rik van Riel
[not found] ` <9lc0ek$l5k$1@ns1.clouddancer.com>
2001-08-15 19:35 ` Colonel
2001-08-15 20:14 ` Admin Mailing Lists
2001-08-15 20:51 ` David Ford [this message]
[not found] ` <9lelsk$bri$1@ns1.clouddancer.com>
2001-08-16 4:27 ` Colonel
2001-08-16 9:27 ` Marco Colombo
2001-08-14 19:13 ` Roy C. Bixler
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=3B7AE0D6.2090804@erisksecurity.com \
--to=david@erisksecurity.com \
--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