From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1962 Path: news.gmane.org!not-for-mail From: Charlie Brady Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Bug for sv status in lsb mode Date: Mon, 13 Jul 2009 10:20:29 -0400 (EDT) Message-ID: References: <8F9355C5-C168-4AD7-8B6C-502416E7EECC@zoy.org> <94175859-2733-4ACF-85E9-DD5FF627F23B@zoy.org> <17A739BC-94BA-4611-A523-6978934F0D61@zoy.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: ger.gmane.org 1247494840 15348 80.91.229.12 (13 Jul 2009 14:20:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Jul 2009 14:20:40 +0000 (UTC) Cc: supervision@list.skarnet.org To: Mathieu Poumeyrol Original-X-From: supervision-return-2197-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Jul 13 16:20:33 2009 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.50) id 1MQMOO-00013i-7w for gcsg-supervision@gmane.org; Mon, 13 Jul 2009 16:20:32 +0200 Original-Received: (qmail 9479 invoked by uid 76); 13 Jul 2009 14:21:45 -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 9469 invoked from network); 13 Jul 2009 14:21:45 -0000 X-X-Sender: charlieb@e-smith.charlieb.ott.istop.com In-Reply-To: <17A739BC-94BA-4611-A523-6978934F0D61@zoy.org> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1962 Archived-At: On Mon, 13 Jul 2009, Mathieu Poumeyrol wrote: >> > What makes you think that sv status should return non-zero if the service >> > is down? I see nothing to suggest that here: >> > >> > http://smarden.sunsite.dk/runit/sv.8.html >> >> It's not explicit here, but required for LSB compliance. >> >> see >> http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html >> >> As a matter of fact, sv code looks like it is meant to achieve this, but >> fails because of the side effect on the "r" global. > > Sorry, it is actually explicit in the "Exit codes" last paragraph... > > If the command is status, it exits 3 if the service is down, and 4 if the > status is unknown. It exits 2 on wrong usage, and 151 on error. Indeed. Sorry for not reading that more carefully myself.