From: Kevin <spamite@ev1.net>
Subject: Re: Should svwaitup/down be built again, or how to make sv do this?
Date: Wed, 12 Jul 2006 11:27:21 -0500 [thread overview]
Message-ID: <200607121127.48966.spamite@ev1.net> (raw)
In-Reply-To: <20060712152013.7834.qmail@01ba84912064b9.315fe32.mid.smarden.org>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Wednesday 12 July 2006 10:20, Gerrit Pape wrote:
> On Tue, Jul 11, 2006 at 08:59:45PM -0500, Kevin wrote:
> > We have some services that have come to depend on behavior of
> > svwaitup/svwaitdown to work. As these are no longer built since
> > runit-1.4.0, we're starting to face a problem, since we use the
> > Debian packaged version:
> >
> > sv -w 1000000 -v check <service> seems to return immediately. We
> > have no way to indefinitely block a service from starting without
> > replacing this functionality with extra code that used to already
> > exist, to our knowledge.
> >
> > Are we missing something?
>
> I'm not sure what exactly you used the svwait* programs for, so I
> cannot say whether or how it works with 'sv check/start/stop'.
>
> Regards, Gerrit.
We cannot make sv block like svwaitup did. Either we're misunderstanding
how to use it, or something.
An example service script is included below:
#!/bin/sh
svwaitup ~/service/sfsagent
exec chpst -e env runthis.sh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-12 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 1:59 Kevin
2006-07-12 15:20 ` Gerrit Pape
2006-07-12 16:27 ` Kevin [this message]
2006-07-13 8:44 ` Gerrit Pape
2006-07-17 17:56 ` Kevin
2006-07-17 19:32 ` Stefan Karrmann
2006-07-18 8:38 ` Uffe Jakobsen
2006-07-19 18:46 ` Kevin
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=200607121127.48966.spamite@ev1.net \
--to=spamite@ev1.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).