From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1197 Path: news.gmane.org!not-for-mail From: Kevin Newsgroups: gmane.comp.sysutils.supervision.general Subject: Should svwaitup/down be built again, or how to make sv do this? Date: Tue, 11 Jul 2006 20:59:45 -0500 Organization: The Dyslexic Chicken Parade Message-ID: <200607112100.08660.spamite@ev1.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart37187130.rCpZZnBmJf"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1152669775 29878 80.91.229.2 (12 Jul 2006 02:02:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 12 Jul 2006 02:02:55 +0000 (UTC) Original-X-From: supervision-return-1433-gcsg-supervision=m.gmane.org@list.skarnet.org Wed Jul 12 04:02:53 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 1G0U3n-0000HS-DZ for gcsg-supervision@gmane.org; Wed, 12 Jul 2006 04:02:43 +0200 Original-Received: (qmail 18207 invoked by uid 76); 12 Jul 2006 02:03:04 -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 18201 invoked from network); 12 Jul 2006 02:03:04 -0000 Original-To: supervision@list.skarnet.org User-Agent: KMail/1.9.3 Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1197 Archived-At: --nextPart37187130.rCpZZnBmJf Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline We have some services that have come to depend on behavior of=20 svwaitup/svwaitdown to work. As these are no longer built since=20 runit-1.4.0, we're starting to face a problem, since we use the Debian=20 packaged version: sv -w 1000000 -v check seems to return immediately. We have no=20 way to indefinitely block a service from starting without replacing this=20 functionality with extra code that used to already exist, to our=20 knowledge. Are we missing something? Thanks for any help you can provide. --nextPart37187130.rCpZZnBmJf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEtFeoeG1uZde00Q4RAr/PAJ4mPxcNrhGt1wngeV7cVYwZOmjz6QCZAVwf asBBwK8v41elfY1ahMVHDFg= =w6JA -----END PGP SIGNATURE----- --nextPart37187130.rCpZZnBmJf--