supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Docs for using runit with upstart
Date: Wed, 01 Nov 2006 05:57:09 -0500	[thread overview]
Message-ID: <87velz3056.fsf@asfast.com> (raw)

I recently posted the following message on the list.smarden.org
mailing list.  I thought it might also be of interest here ...

There's a replacement for /etc/inittab processing called "upstart" that
is currently being used in Ubuntu linux and possibly other places (see
http://upstart.ubuntu.com/).  I got runit going under this environment,
and I thought it would be useful to add upstart instructions to the
"runit - use with traditional init" documentation that's located at
http://smarden.org/runit/useinit.html

I'd like to offer the following documentation to be added right below
the "Using with sysvinit" section:

  Using with sysvinit and upstart

  If your system uses a sysvinit alike init scheme that utilizes
  upstart instead of inittab, and which has start and stop scripts
  located in /etc/event.d, do:

   # cat >/etc/event.d/SV <<EOT
   # for runit - manage /sbin/runsvdir-start
   start on runlevel-2
   start on runlevel-3
   start on runlevel-4
   start on runlevel-5
   stop on shutdown
   respawn /sbin/runsvdir-start
   EOT

  and tell init to re-read its configuration, e.g.:

   # init q

As part of this, I'd also recommend changing the current heading
"Using with sysvinit" to "Using with sysvinit and inittab", or
some such thing.


-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.



             reply	other threads:[~2006-11-01 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 10:57 Lloyd Zusman [this message]
2006-11-01 11:45 ` Gerrit Pape

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=87velz3056.fsf@asfast.com \
    --to=ljz@asfast.com \
    /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).