From: Charles Duffy <cduffy@spamcop.net>
Subject: Re: new "sv status" flags and exit-tracking patch, and misc.
Date: Thu, 08 Dec 2005 13:37:51 -0600 [thread overview]
Message-ID: <dna22i$uro$1@sea.gmane.org> (raw)
In-Reply-To: <20051208110807.32074.qmail@a42d0fe2c911e1.315fe32.mid.smarden.org>
Gerrit Pape wrote:
> On Mon, Sep 26, 2005 at 10:12:20AM +0000, Gerrit Pape wrote:
>>Hi Charles, thanks a lot for the patch. This looks much better to me to
>>work with. I'll try to find some time soon, to review it, and integrate
>>it into the next runit test version.
>
> Hi, I haven't done this yet, sorry. Somehow I'm reluctant to make these
> changes to the command line option of the sv program, I'm afraid it gets
> too complex.
>
> I guess ./run and ./finish almost always will be scripts, more precisely
> shell scripts. runsv as of now maintains two files supervise/stat and
> supervise/pid. How about removing these files, and add a single one
> containing the informations discussed here?:
>
> ./supervise/info:
> <state> <want> <pid> <uptime> <runrc> <finishrc>
Sounds reasonable. Are you willing to impliment this yourself, or do you
want me to?
next prev parent reply other threads:[~2005-12-08 19:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 4:46 Charles Duffy
2005-09-17 5:17 ` Mike Bell
2005-09-19 8:35 ` Gerrit Pape
2005-09-17 8:53 ` Laurent Bercot
2005-09-19 8:31 ` Gerrit Pape
2005-09-19 16:04 ` Charles Duffy
2005-09-19 19:13 ` Charles Duffy
2005-09-21 21:50 ` new "sv status" flags and exit-tracking patch, yet again Charles Duffy
2005-09-26 10:12 ` new "sv status" flags and exit-tracking patch, and misc Gerrit Pape
2005-09-26 15:31 ` duplicate processes Jussi Ramo
2005-09-26 15:42 ` Charlie Brady
2005-12-08 11:08 ` new "sv status" flags and exit-tracking patch, and misc Gerrit Pape
2005-12-08 19:37 ` Charles Duffy [this message]
2005-12-09 14:29 ` Gerrit Pape
2005-12-09 14:50 ` Rafal Bisingier
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='dna22i$uro$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).