From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1202 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: Mon, 17 Jul 2006 12:56:08 -0500 Organization: The Dyslexic Chicken Parade Message-ID: <200607171256.14899.spamite@ev1.net> References: <200607112100.08660.spamite@ev1.net> <200607121127.48966.spamite@ev1.net> <20060713084421.7943.qmail@0c0c26b6d83f02.315fe32.mid.smarden.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1311438.7qUMYPET2C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1153158977 7366 80.91.229.2 (17 Jul 2006 17:56:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 17 Jul 2006 17:56:17 +0000 (UTC) Original-X-From: supervision-return-1438-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Jul 17 19:56:16 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 1G2XK5-00022R-0c for gcsg-supervision@gmane.org; Mon, 17 Jul 2006 19:56:01 +0200 Original-Received: (qmail 23057 invoked by uid 76); 17 Jul 2006 17:56:21 -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 23051 invoked from network); 17 Jul 2006 17:56:21 -0000 Original-To: supervision@list.skarnet.org User-Agent: KMail/1.9.3 In-Reply-To: <20060713084421.7943.qmail@0c0c26b6d83f02.315fe32.mid.smarden.org> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1202 Archived-At: --nextPart1311438.7qUMYPET2C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 13 July 2006 03:44, Gerrit Pape wrote: > > 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 > > svwaitup did wait two seconds by default after the sfsagent service > daemon has been started, this seems to be what you relied on. Indeed, > sv doesn't do that by default, but it supports the ./check script > instead. svwaitup waited until the service had been running for at least 2 seconds=20 before exiting, no? > If you want 'sv start ~/service/sfsagent' or 'sv check > ~/service/sfsagent' to wait for two seconds before returning, simply do > 'sleep 2' in ~/service/sfsagent/check. That would be a useless check. What we want is for the sfsagent service=20 to be running, not just wait 2 seconds before starting. > Better yet, find out how to check for what the sfsagent service daemon > needs to provide before runthis.sh can be started, and check for that > in ~/service/sfsagent/check. So, it sounds like you're saying that the functionality of checking for a=20 service to be running, and waiting until that service is running before=20 continuing no longer exists in runit as it is presently built. Is this=20 correct? --nextPart1311438.7qUMYPET2C Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBEu88+eG1uZde00Q4RAppWAJ4jxUyldnBHx0KlGXSjb5P3fDLyAgCeLkZE YYLgxanBUxRUCvFhXu5XWZs= =vdQo -----END PGP SIGNATURE----- --nextPart1311438.7qUMYPET2C--