From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1064 Path: news.gmane.org!not-for-mail From: Alex Efros Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: service definition vs service activation Date: Tue, 7 Mar 2006 20:35:22 +0200 Organization: asdfGroup Inc., http://powerman.asdfGroup.com/ Message-ID: <20060307183522.GB17273@home.power> References: <20060306160542.18689.qmail@036bc12a5086b2.315fe32.mid.smarden.org> <20060306111338.2d8151ff@alloy.copperisle.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1141756535 1983 80.91.229.2 (7 Mar 2006 18:35:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 7 Mar 2006 18:35:35 +0000 (UTC) Original-X-From: supervision-return-1300-gcsg-supervision=m.gmane.org@list.skarnet.org Tue Mar 07 19:35:33 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1FGh1o-0003YX-QO for gcsg-supervision@gmane.org; Tue, 07 Mar 2006 19:35:25 +0100 Original-Received: (qmail 2966 invoked by uid 76); 7 Mar 2006 18:35:46 -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 2960 invoked from network); 7 Mar 2006 18:35:46 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060306111338.2d8151ff@alloy.copperisle.com> User-Agent: Mutt/1.5.11 Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1064 Archived-At: Hi! On Mon, Mar 06, 2006 at 11:13:38AM -0800, Wayne Marshall wrote: > On the other hand here has been no usual custom or consensus for the > service definition directory. This is because services combine > attributes of things usually found elsewhere, such > as /etc, /etc/init.d, /var/run, and /var/log. Service definitions by > their very nature don't exactly fit cleanly anywhere in the usual unix > hier(7) scheme of things. I'm mostly agree with your, but there exists two more alternatives: 1) Service definition directory can use symlinks to suit FHS: /etc/sv/SERVICE/supervise -> /var/run/sv/SERVICE/ /etc/sv/SERVICE/log/supervise -> /var/run/sv/SERVICE/log/ and ./log/run can start svlogd with /var/log/SERVICE/ as param. That way /etc/ will contain only static configuration files, while logs and ./supervise/ dir will be on /var/. Service activation directory is /var/service/ or /var/sv/. I've tried this way, and found myself always forget to create ./supervise symlinks BEFORE I start new service and runsv will create ./supervise directories instead. This can be easy solved by using script to create service directories, of course. Ugly, but suit FHS. 2) DJB invented nice place where to create directories which is not suit FHS. In root. ;-) From this view, /sv/ or /service/ would be nice place for service definition directory, while /var/sv/ or /var/service/ is service activation directory. P.S. I use /service/ as service definition directory, /var/service/ as service activation directory, and ./log/run start svlogd with /var/log/SERVICE/ param. -- WBR, Alex.