[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Clusterwide pids

To: linux-cluster@nl.linux.org
Subject: Re: Clusterwide pids
From: Lars Marowsky-Bree <lmb@suse.de>
Date: Wed, 11 Jul 2001 10:22:46 +0200
In-Reply-To: <200107110440.f6B4eO6405214@saturn.cs.uml.edu>; from "Albert D. Cahalan" on 2001-07-11T00:40:24
References: <20010710235649.WZCR22093.imf16bis.bellsouth.net@taz> <200107110440.f6B4eO6405214@saturn.cs.uml.edu>
Sender: owner-linux-cluster@nl.linux.org
User-Agent: Mutt/1.3.16i

On 2001-07-11T00:40:24,
   "Albert D. Cahalan" <acahalan@cs.uml.edu> said:

> How about this: when a node boots, pass it a PID range.

This leaves us with the chicken and egg problem - how do you boot a node which
is - at the time of boot - unable to contact the cluster?

IMHO, a node should be able to have "local" processes (node id part of the
CPID = 0). Only after it joined the cluster once (and thus was assigned a node
id) should processes which need a valid CPID be started.

Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Perfection is our goal, excellence will be tolerated. -- J. Yahl


Linux-cluster: generic cluster infrastructure for Linux
Archive:       http://mail.nl.linux.org/linux-cluster/

Follow-Ups:
- Re: Clusterwide pids
  - From: "Albert D. Cahalan" <acahalan@cs.uml.edu>

References:
- re[2]: Clusterwide pids
  - From: Greg Freemyer <freemyer@NorcrossGroup.com>
- Re: re[2]: Clusterwide pids
  - From: "Albert D. Cahalan" <acahalan@cs.uml.edu>

Prev by Date: Re: Clusterwide pids
Next by Date: Re: Clusterwide pids
Prev by thread: Re: re[2]: Clusterwide pids
Next by thread: Re: Clusterwide pids
Index(es):
- Date
- Thread