From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/854 Path: news.gmane.org!not-for-mail From: Charles Duffy Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit - access to run script's exit status for finish? Date: Sat, 27 Aug 2005 17:56:34 -0500 Message-ID: References: <20050529055250.21848.qmail@eea771e6cc397c.315fe32.mid.smarden.org> <20050530074233.GA17439@skarnet.org> <20050531114539.16382.qmail@6607a8c5b39a0b.315fe32.mid.smarden.org> <20050531190911.25938.qmail@adf4e649eec508.315fe32.mid.smarden.org> <20050601000521.GB32490@grummit.biaix.org> <20050827192438.24239.qmail@573d30f8a31845.315fe32.mid.smarden.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1125183854 21712 80.91.229.2 (27 Aug 2005 23:04:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 27 Aug 2005 23:04:14 +0000 (UTC) Original-X-From: supervision-return-1090-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Aug 28 01:04:12 2005 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1E99iV-0005cq-BI for gcsg-supervision@gmane.org; Sun, 28 Aug 2005 01:04:03 +0200 Original-Received: (qmail 13297 invoked by uid 76); 27 Aug 2005 23:04:24 -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 13291 invoked from network); 27 Aug 2005 23:04:24 -0000 X-Injected-Via-Gmane: http://gmane.org/ Original-To: supervision@list.skarnet.org Original-Lines: 23 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: fwext1-ext.isgenesis.com User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux)) Original-Sender: news Xref: news.gmane.org gmane.comp.sysutils.supervision.general:854 Archived-At: On Sat, 27 Aug 2005 19:24:35 +0000, Gerrit Pape wrote: > I still don't know what's the best way to pass this information to the > ./finish script. Providing the exit code of ./run through the > environment seems to be the best solution, but (1) only the ./finish > script's environment should be altered, not the ./run script's, and (2) > runsv currently doesn't allocate memory dynamically, I don't want to > change that. Hmm. I suppose doing an unsetenv() is unacceptable because it would interfere wih run's environment if run had set (or was expecting the outside world to set) a variable with the same name. Personally, to be honest, I'd consider this acceptable so long as it was documented and the chosen name was unlikely to collide with anything -- but even so, I can appreciate our reluctance to go this route. Your suggestion of stuffing it in the status file makes sense, then -- but a convenient way to get the info still out is still needed. How about having an argument to runsvstat to retrieve *only* this piece of information? (For that matter, being able to do the same with other data in the status file would be likewise useful).