From owner-freebsd-hackers Thu Jun 14 7:39:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D39FB37B407 for ; Thu, 14 Jun 2001 07:39:26 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f5EEYlf26283; Thu, 14 Jun 2001 10:34:47 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 14 Jun 2001 10:34:47 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Robert Withrow Cc: Cyrille Lefevre , freebsd-hackers@FreeBSD.ORG Subject: Re: import NetBSD rc system In-Reply-To: <200106141357.JAA27316@pobox.engeast.BayNetworks.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG To do some of the hierarchal start/stop at runtime stuff, you really need a stateful rc system that stores its start/stop state in /var/run/rc.d or the like. In this way, the system could track various activities and know which dependencies were already started. However, this has a number of limitations, including differentiating the start/stop status of the daemon vs. its script, behavior in an environment under development, etc. Transarc's AFS product has a notion of a "boss server" that starts and stops services associated with AFS. It has the added benefit of detecting service failures, logging them, and performing specified restart behavior (such as: oh, it failed. log that. try starting it. oh, it failed again, and within five minutes, so send a louder log message. Damn, it failed again! And within five minutes! Screw that, page the admin and stop trying). A powerful tool, although a lot more complex, and maps poorly into the breadth of services (and their management models) that we ship. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Thu, 14 Jun 2001, Robert Withrow wrote: > > clefevre-lists@noos.fr said: > :- oops, rc2 isn't started. too bad. > > I think that is exactly the desired design. The > RC *system* starts things correctly, but the manager, > *bypassing* the RC *system* can start and stop things > exactly as he wished. For debugging or whatever. > > I'd argue that if you want to start/stop a *subtree*, you > should ask the RC *system* to do that somehow. > > -- > Robert Withrow -- (+1 978 288 8256, ESN 248) > BWithrow@NortelNetworks.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message