From owner-freebsd-hackers Sun Jun 17 8:54:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7ve.mailsrvcs.net (smtp7vepub.gte.net [206.46.170.28]) by hub.freebsd.org (Postfix) with ESMTP id 73D7337B401 for ; Sun, 17 Jun 2001 08:54:25 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-11.nnj.dialup.bellatlantic.net [151.198.117.11]) by smtp7ve.mailsrvcs.net (8.9.1/8.9.1) with ESMTP id PAA34158860; Sun, 17 Jun 2001 15:53:20 GMT Message-ID: <3B2CD26F.ACD430B0@bellatlantic.net> Date: Sun, 17 Jun 2001 11:53:19 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Cyrille Lefevre Cc: tlambert2@mindspring.com, Robert Withrow , freebsd-hackers@FreeBSD.ORG Subject: Re: import NetBSD rc system References: <200106141357.JAA27316@pobox.engeast.BayNetworks.COM> <3B29B98E.DAF2ABE4@mindspring.com> <3B2A9F60.A12AB917@bellatlantic.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit 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 Cyrille Lefevre wrote: > > Sergey Babkin writes: > [snip] > > How about keeping the state of the system as empty files in > > a subdirectory, say, /etc/rcstate.d. This directory would be > > cleaned up at boot time and then as each of the service startup > > script is run (and completed successfully), an empty file with the > > same name would be created in this directory. Reversely, when a > > service shutdown script is completed (or started ?), the state > > file is removed. This will allow to define the run states easily > > as empty rc scripts containing only dependency information in them. > > how about if a service die or started w/o the rc subsystem ? Remove or create this indicator file manually ? I mean, as an easy solution. The complex solution is of course to monitor the status of the service and react accordingly if it fails. After (if) such thing would be implemented, adding of the rest of the high-availability cluster support will be obvious :-) -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message