supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: supervision@list.skarnet.org
Subject: svwaitup/check
Date: Thu, 29 Mar 2007 09:36:45 +0100 (WEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703290916010.24990@jmaa.math.ist.utl.pt> (raw)

I'm trying to setup the network "service" with a run script like this:
 	#!/bin/bash
 	exec 2>&1
 	echo "*** Bringing up network..."
 	# wait for ulogd...
 	exec /etc/sysconfig/network-devices/ifup eth0

The system is LFS. The finish script will just "touch down". This means
I'm considering the task of bringing up the network as a one-time
initialization task, not a real service. But I want the network to start
after ulogd is up, and the latter is a real service, hence this
workaround to start network in stage2. (Comments/suggestions would be
appreciated. I'm familiar with daemontools, but I'm just starting with
runit.)

Now, as for the "wait for ulogd" part, the hint I found is the use of
svwaitup in http://smarden.org/pape/djb/daemontools/noinit.html. The
"svwaitup" link is broken and I'm assuming that it belongs to an older
release. I'm using the current developement one.
I suppose it should be done with sv, using the check command. Something
like this?
 	sv -w 3 check ????? ulogd || exit 1
How to "request a state" of the ulogd service? This part of the man page
is not clear to me.
Moreover, if the ./check script exists then sv check will not report to
STDOUT but will rather execute ./check. Is this correct?

TIA,

Jorge Almeida


             reply	other threads:[~2007-03-29  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29  8:36 Jorge Almeida [this message]
2007-03-29 14:03 ` svwaitup/check Charlie Brady
2007-03-29 14:29   ` svwaitup/check Jorge Almeida

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=Pine.LNX.4.64.0703290916010.24990@jmaa.math.ist.utl.pt \
    --to=jalmeida@math.ist.utl.pt \
    --cc=supervision@list.skarnet.org \
    /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).