From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1200 Path: news.gmane.org!not-for-mail From: Kevin Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Should svwaitup/down be built again, or how to make sv do this? Date: Wed, 12 Jul 2006 11:27:21 -0500 Organization: The Dyslexic Chicken Parade Message-ID: <200607121127.48966.spamite@ev1.net> References: <200607112100.08660.spamite@ev1.net> <20060712152013.7834.qmail@01ba84912064b9.315fe32.mid.smarden.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1572309.FXlMs3cygg"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1152721774 28798 80.91.229.2 (12 Jul 2006 16:29:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 12 Jul 2006 16:29:34 +0000 (UTC) Original-X-From: supervision-return-1436-gcsg-supervision=m.gmane.org@list.skarnet.org Wed Jul 12 18:29:28 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1G0hZ0-0003vL-QS for gcsg-supervision@gmane.org; Wed, 12 Jul 2006 18:27:50 +0200 Original-Received: (qmail 5060 invoked by uid 76); 12 Jul 2006 16:28:11 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 5054 invoked from network); 12 Jul 2006 16:28:11 -0000 Original-To: supervision@list.skarnet.org User-Agent: KMail/1.9.3 In-Reply-To: <20060712152013.7834.qmail@01ba84912064b9.315fe32.mid.smarden.org> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1200 Archived-At: --nextPart1572309.FXlMs3cygg Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 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=20 how to use it, or something. An example service script is included below: #!/bin/sh svwaitup ~/service/sfsagent exec chpst -e env runthis.sh --nextPart1572309.FXlMs3cygg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEtSMEeG1uZde00Q4RAm1aAKCa8QSJ6whp76Apt2qPJSDa+UrI/ACfVYQV FPbJ2CAf0R86Ua+cPicVu50= =Mxs8 -----END PGP SIGNATURE----- --nextPart1572309.FXlMs3cygg--