From: prj@po.cwru.edu (Paul Jarc)
Cc: Alex Efros <powerman@powerman.asdfGroup.com>,
supervision@list.skarnet.org
Subject: Re: unable to open supervise/ok: file does not exist
Date: Sat, 05 Aug 2006 15:01:33 -0400 [thread overview]
Message-ID: <m31wrv0zx7.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <EA391AA4-1639-4F40-9A8C-A66D631A612A@gmail.com> (John Butler's message of "Sat, 5 Aug 2006 09:00:56 -0700")
John Butler <imtall@gmail.com> wrote:
> if you get the error "unable to open supervise/ok: file does not
> exist", make sure you are running runsvdir:
>
> runsvdir /var/service &
You shouldn't do that from your interactive shell, though. You should
add runsvdir to your system startup scripts, as described in the
documentation:
http://smarden.org/runit/useinit.html
paul
next prev parent reply other threads:[~2006-08-05 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 1:31 John Butler
2006-08-05 8:22 ` Alex Efros
2006-08-05 16:00 ` John Butler
2006-08-05 19:01 ` Paul Jarc [this message]
2006-08-05 18:59 ` Paul Jarc
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=m31wrv0zx7.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=powerman@powerman.asdfGroup.com \
--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).