From owner-freebsd-hackers  Tue May 20 10:55:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA15699
          for hackers-outgoing; Tue, 20 May 1997 10:55:27 -0700 (PDT)
Received: from precipice.shockwave.com (ppp-206-170-6-9.rdcy01.pacbell.net [206.170.6.9])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15689
          for <hackers@freebsd.org>; Tue, 20 May 1997 10:55:21 -0700 (PDT)
Received: from shockwave.com (localhost [127.0.0.1]) by precipice.shockwave.com (8.8.5/8.7.3) with ESMTP id KAA13245 for <hackers@freebsd.org>; Tue, 20 May 1997 10:55:16 -0700 (PDT)
Message-Id: <199705201755.KAA13245@precipice.shockwave.com>
To: hackers@freebsd.org
Subject: process monitoring tool (like SysV init)?
Date: Tue, 20 May 1997 10:55:16 -0700
From: Paul Traina <pst@shockwave.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I was thinking of hacking up a small program that would read a configuration
file and then spawn and monitor the health of several child processes based
on the contents of the configuration file.

If one of the programs dies, it should restart it.  If it dies too quickly,
it should back-off and log some error messages, ...

This looks and feels a lot like a lobotomized system 5 init program.

Before I actually whack one out -- has anyone seen source code for
something that has basicly these kinds of features already done for
BSD?

Paul