From owner-freebsd-ports Thu Sep 21 07:44:52 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA07761 for ports-outgoing; Thu, 21 Sep 1995 07:44:52 -0700 Received: from Wit401402.student.utwente.nl (Wit401402.student.utwente.nl [130.89.236.162]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA07755 ; Thu, 21 Sep 1995 07:44:48 -0700 Received: (from alain@localhost) by Wit401402.student.utwente.nl (8.6.12/8.6.9) id QAA00423; Thu, 21 Sep 1995 16:44:25 +0200 Date: Thu, 21 Sep 1995 16:44:24 +0200 (MET DST) From: Alain Kalker Reply-To: A.C.P.M.Kalker@student.utwente.nl To: Stephen McKay cc: patl@asimov.volant.org, syssgm@devetir.qld.gov.au, ports@freebsd.org, hackers@freebsd.org Subject: Re: ports startup scripts In-Reply-To: <199509211256.WAA17842@orion.devetir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org Precedence: bulk On Thu, 21 Sep 1995, Stephen McKay wrote: > All those fiddly little scripts give me the irrits too. Half of them run > 'ps' in a reckless manner on shutdown in a hope-I-got-it-right attempt to > find the server they want to kill. Some do that on startup too! > > They are a feeble attempt at enabling and disabling services. If we want > that sort of thing, let's build some sort of super-server (like init or inetd) > to look after them properly (plus some system admin tool to flip them on > and off, and maybe keep track of dependencies on other servers). Let's not > embrace this particular bit of System V. Now _this_ looks like a very interesting idea to me! Just my humble expression of opinion. --- Alain