From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: RE: Runit on sl3
Date: Fri, 26 May 2006 18:43:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0605261841480.5608@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <7231C15EAC2F164CA6DC326D97493C8B01C1DE3F@exchange35.fed.cclrc.ac.uk>
On Fri, 26 May 2006, Nandakumar, R (Raja) wrote:
> Runsvdir also does not become a background process automatically.
Correct. You either haven't read http://smarden.org/runit/useinit.html or
you have chosen to do things in some way other than what is documented
there. That would be unwise. It's good advice.
---
Charlie
next prev parent reply other threads:[~2006-05-26 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 9:56 Nandakumar, R (Raja)
2006-05-26 20:18 ` Charlie Brady
2006-05-26 20:59 ` Nandakumar, R (Raja)
2006-05-26 22:43 ` Charlie Brady [this message]
2006-05-26 22:47 ` Nandakumar, R (Raja)
2006-05-26 22:59 ` Charlie Brady
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.61.0605261841480.5608@e-smith.charlieb.ott.istop.com \
--to=charlieb-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).