Re: Should svwaitup/down be built again, or how to make sv do this?

[Gerrit Pape <pape@smarden.org>]

On Wed, Jul 12, 2006 at 11:27:21AM -0500, Kevin wrote:
> On Wednesday 12 July 2006 10:20, Gerrit Pape wrote:
> > 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'.

> 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.

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.

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.

E.g., the ./check script from the socklog-unix service runs a tiny
program that tries to connect to the /dev/log socket, without writing
anything to it, and only exits zero if the connect succeeds.  This makes
'sv start socklog-unix' wait until the socklog service daemon is
listening on /dev/log, and accepts local log messages.

Regards, Gerrit.