From: Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Testing runit-init, stuck in stage 2 ???
Date: Sat, 26 Jun 2004 18:29:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0406261826540.2967-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <m3smciuism.fsf@asfast.com>
On Sat, 26 Jun 2004, Lloyd Zusman wrote:
> I figured this out. Based on the contents of my /etc/inittab, I needed
> to make my /etc/runit/1 look like the following:
...
> /etc/rc.d/rc.sysinit
> /etc/rc.d/rc 5
...
> I had commented out the "rcS" and "rmnologin" calls, but I had forgotten
> to add the "rc.sysinit" and "rc 5" calls.
You won't want "rc 5" there. That's equivalent to what you should be doing
in /etc/runit/2 (which you tell us you already have set up - at least the
runsvdir part thereof). You are unlikely to need to change (much) the
example /etc/runit/2 script.
---
Charlie
next prev parent reply other threads:[~2004-06-26 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 19:41 Lloyd Zusman
2004-06-26 21:10 ` Lloyd Zusman
2004-06-26 22:29 ` Charlie Brady [this message]
2004-06-26 23:13 ` Lloyd Zusman
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.44.0406261826540.2967-100000@e-smith.charlieb.ott.istop.com \
--to=charlieb-smarden-supervision@budge.apana.org.au \
--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).