public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: WANTED: Re: VM lockup with 2.4.8 / 2.4.8pre8
Date: Wed, 15 Aug 2001 21:27:34 -0700 (PDT)	[thread overview]
Message-ID: <20010816042734.D3E7C783F5@mail.clouddancer.com> (raw)
In-Reply-To: <9lelsk$bri$1@ns1.clouddancer.com>
In-Reply-To: <Pine.LNX.4.10.10108151612000.9584-100000@athena.intergrafix.net> <20010815193521.4DDE8783F5@mail.clouddancer.com> <9lelsk$bri$1@ns1.clouddancer.com>

In clouddancer.list.kernel, you 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.
>> 
>
>agreed, but FWIW my postfix master daemon is pid 434


Ah, yes that reminds me that when you take down a service and then
start it again, you lose that nice low pid.  FWIW, my master is 23034
now.  As D Ford stated, paying attention to pid value is not useful.


-- 
Windows 2001: "I'm sorry Dave ...  I'm afraid I can't do that."


  parent reply	other threads:[~2001-08-16  4:27 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
     [not found]       ` <9lelsk$bri$1@ns1.clouddancer.com>
2001-08-16  4:27         ` Colonel [this message]
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=20010816042734.D3E7C783F5@mail.clouddancer.com \
    --to=klink@clouddancer.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