From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Earl Chew <earl_chew@agilent.com>
Cc: supervision@list.skarnet.org
Subject: Re: svwaitup races with sv
Date: Fri, 24 Jul 2009 16:31:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0907241627160.18966@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <4A635477.6030503@agilent.com>
On Sun, 19 Jul 2009, Earl Chew wrote:
> The script below generates the following output:
>
>> down: ./svc: 0s
>> svwaitup: warning: ./svc: is down.
>> .... WaitUp 1
>> Try again
>> run: ./svc: (pid 8496) 2s, normally down, want down
>
> It illustrates a race between runsv/sv and svwaitup.
...
> It would be better if sv(8) itself could synchronise.
I think that would be possible by making the fifo unbuffered, and having
sv inject a nop command during 'sv status' (so sv would be blocked until
runsv had processed previous commands). But that would change the timing
of lots of current programs which call 'sv'.
next prev parent reply other threads:[~2009-07-24 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 8:00 Bug for sv status in lsb mode Mathieu Poumeyrol
2009-07-13 13:42 ` Charlie Brady
2009-07-13 14:13 ` Mathieu Poumeyrol
2009-07-13 14:18 ` Mathieu Poumeyrol
2009-07-13 14:20 ` Charlie Brady
2009-07-17 9:08 ` Gerrit Pape
2009-07-17 10:02 ` Mathieu Poumeyrol
2009-07-17 11:08 ` Gerrit Pape
2009-07-19 14:52 ` sv sometimes won't issue down request Earl Chew
2009-07-19 17:14 ` svwaitup races with sv Earl Chew
2009-07-24 20:31 ` Charlie Brady [this message]
2009-07-24 20:35 ` Earl Chew
2009-07-24 20:18 ` sv sometimes won't issue down request (specifically, after 'sv once xxx') Charlie Brady
2009-07-24 20:38 ` Earl Chew
2009-07-24 21:01 ` Charlie Brady
2009-07-25 19:49 ` Joan Picanyol i Puig
2009-07-27 9:09 ` sv sometimes won't issue down request Gerrit Pape
2009-07-27 17:39 ` Earl Chew
2010-05-31 19:54 ` Bug for sv status in lsb mode Erik Wright
2010-06-03 9:04 ` Gerrit Pape
2010-06-03 14:12 ` Erik Wright
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=Pine.LNX.4.64.0907241627160.18966@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=earl_chew@agilent.com \
--cc=supervision@list.skarnet.org \
/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).