From: Alex Efros <powerman@powerman.name>
To: supervision@list.skarnet.org
Subject: Re: Installing on Centos
Date: Tue, 7 May 2013 13:56:25 +0300 [thread overview]
Message-ID: <20130507105625.GA2125@home.power> (raw)
In-Reply-To: <CALxYQy4G_Koya4VNmi4PGpy7p7hY8avvtuFpNdkjr0cL3BxMSA@mail.gmail.com>
Hi!
On Tue, May 07, 2013 at 10:30:15AM +0100, Peter Hickman wrote:
> No problem with that (so far) but when I compare it to my Ubuntu 10.04
> installation I seem to be missing things like
I didn't installed runit from source for years, so I may be wrong, but:
> 1) /etc/sv and /etc/service
Runit doesn't hardcoded to use some predefined directory, you can put your
services in any directory you like - /service or /etc/sv - you choose.
So, neither of these directories created automatically when installing
runit - you've to create them yourself. Some linux distributives when
creating packages for runit make this decision instead of you and
preconfigure runit in some way, which include creating such directories.
> 2) When is ps ax it does not appear to be running anywhere...
That's because you didn't started it, I suppose. :)
> 3) The sv command only seems to be available to root, unlike on Ubunto
> where other accounts can access it
Check your $PATH, different distributives configure it in different ways -
some include */sbin/ directories in $PATH for non-root users, others don't.
Same for /usr/local/{bin,sbin}/. Check where your runit's binaries was
installed and is that directory included in non-root's $PATH.
--
WBR, Alex.
next prev parent reply other threads:[~2013-05-07 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 9:30 Peter Hickman
2013-05-07 10:56 ` Alex Efros [this message]
2013-05-07 11:17 ` Peter Hickman
2013-05-07 17:47 ` Joshua Timberman
2013-05-09 13:03 ` Peter Hickman
2013-05-09 14:49 ` Charlie Brady
2013-05-09 15:05 ` Peter Hickman
2013-05-09 15:08 ` Charlie Brady
2013-05-09 15:37 ` Joshua Timberman
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=20130507105625.GA2125@home.power \
--to=powerman@powerman.name \
--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).