From: Charles Duffy <cduffy@spamcop.net>
Subject: Re: runit - access to run script's exit status for finish?
Date: Fri, 26 Aug 2005 15:30:23 -0500 [thread overview]
Message-ID: <pan.2005.08.26.20.30.21.804985@spamcop.net> (raw)
In-Reply-To: <20050601000521.GB32490@grummit.biaix.org>
On Wed, 01 Jun 2005 02:05:21 +0200, Joan Picanyol i Puig wrote:
> * Gerrit Pape <pape@smarden.org> [20050531 21:07]:
>> On Tue, May 31, 2005 at 10:28:25AM -0400, Paul Jarc wrote:
>> >
>> > Environment variables make that easy. How about setting $RUN_STATUS?
>>
>> But on the other hand this is a change to the process state of all
>> service daemons, currently their environment is well-defined through
>> /etc/runit/2, or runsvdir-start.
>>
>> What about adding the return code to ./supervise/status?
>
> I usually empty the environment in my run scripts, so I'd prefer this
> solution.
I thought the format of supervise/status was opaque, and prone to changing
between releases. Am I incorrect? (Certainly, it doesn't look trivial to
parse from a shell script).
Also, what's the status of this enhancement?
next prev parent reply other threads:[~2005-08-26 20:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 16:26 Charles Duffy
2005-05-29 5:52 ` Gerrit Pape
2005-05-30 7:42 ` Laurent Bercot
2005-05-31 11:49 ` Gerrit Pape
2005-05-31 14:28 ` Paul Jarc
2005-05-31 19:09 ` Gerrit Pape
2005-06-01 0:05 ` Joan Picanyol i Puig
2005-08-26 20:30 ` Charles Duffy [this message]
2005-08-27 19:24 ` Gerrit Pape
2005-08-27 22:56 ` Charles Duffy
2005-08-29 8:12 ` Gerrit Pape
2005-08-29 10:08 ` Charles Duffy
2005-08-30 11:06 ` Gerrit Pape
2005-08-30 16:55 ` Charles Duffy
2005-09-01 9:13 ` Gerrit Pape
2005-09-12 15:11 ` Charles Duffy
2005-09-15 9:33 ` Gerrit Pape
2005-09-15 12:18 ` Paul Jarc
2005-09-15 14:46 ` Gerrit Pape
2005-09-15 18:10 ` Charles Duffy
2005-09-16 8:15 ` Gerrit Pape
2005-08-27 23:01 ` Charles Duffy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2005.08.26.20.30.21.804985@spamcop.net \
--to=cduffy@spamcop.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).