From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/775 Path: news.gmane.org!not-for-mail From: Payal Rathod Newsgroups: gmane.comp.sysutils.supervision.general Subject: OT: /package and /service Date: Tue, 19 Apr 2005 14:39:07 -0400 Message-ID: <20050419183907.GA28253@tranquility.scriptkitchen.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1113935714 6274 80.91.229.2 (19 Apr 2005 18:35:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 19 Apr 2005 18:35:14 +0000 (UTC) Original-X-From: supervision-return-1011-gcsg-supervision=m.gmane.org@list.skarnet.org Tue Apr 19 20:35:11 2005 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1DNxYm-0006hF-DV for gcsg-supervision@gmane.org; Tue, 19 Apr 2005 20:34:56 +0200 Original-Received: (qmail 27859 invoked by uid 76); 19 Apr 2005 18:39:29 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 27853 invoked from network); 19 Apr 2005 18:39:29 -0000 Original-To: supervision@list.skarnet.org Content-Disposition: inline User-Agent: Mutt/1.5.8i Xref: news.gmane.org gmane.comp.sysutils.supervision.general:775 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:775 Hi, I am not sure where exactly these questions belong to. I am taking the liberty to post them here. Please excuse. 1. Why is /package made with sticky bit set? 2. In /service//supervise/ there are 4 files, 2 fifos - control and ok 2 normal files - lock and status Why are fifos used here? Which document explains this? 3. On cr.yp.to it says that, "svscanboot starts svscan in the /service directory, ..." "svscan starts one supervise process ... " "svscan is designed to run forever. " I understand that if process under service dies svscan starts it again. But what about svscan itself? What if it dies? Who restarts it? Reading the script /command/svscanboot did not help much. Also is there any documentation which says why are there so many dots in that script and what do they signify? Thanks in advance. With warm regards, -Payal