From: Charles Duffy <cduffy@spamcop.net>
Subject: Re: runit - access to run script's exit status for finish?
Date: Thu, 15 Sep 2005 13:10:04 -0500 [thread overview]
Message-ID: <dgcde0$par$1@sea.gmane.org> (raw)
In-Reply-To: <20050915144140.2536.qmail@1c84fcc3458bfc.315fe32.mid.smarden.org>
Gerrit Pape wrote:
> On Thu, Sep 15, 2005 at 08:18:06AM -0400, Paul Jarc wrote:
>
>>Gerrit Pape <pape@smarden.org> wrote:
>>
>>> # sv status -r .
>>> #
>>>./run didn't terminate yet, since the supervisor started.
>>
>>Since the supervisor started, or since the last time ./run was
>>started? The latter seems more useful to me.
>
> Yes, I agree. It should print nothing if ./run (or ./finish with -f) is
> currently running.
That's not very useful when chaining, though.
If you run "sv status -r -p -s ." in a shell script, you're probably
going to pipe it into something like "read exitstatus pid state";
excluding the exit status entirely if the program is currently running,
then, means that you'd end up with your values stored in the wrong
variables -- certainly not a desirable outcome.
At minimum, a placeholder like "-" or "N/A" should be printed if one
desires to indicate that no exit has occured. (That said, I'm still fond
of my type:value syntax).
next prev parent reply other threads:[~2005-09-15 18:10 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
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 [this message]
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='dgcde0$par$1@sea.gmane.org' \
--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).