supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Peter Hickman <peterhickman386@googlemail.com>
Cc: "<supervision@list.skarnet.org>" <supervision@list.skarnet.org>
Subject: Re: Installing on Centos
Date: Thu, 9 May 2013 14:03:53 +0100	[thread overview]
Message-ID: <CALxYQy4Kzb7LOza80icg1CBBeHan_DXPGne1JzPuqfT_3stB5g@mail.gmail.com> (raw)
In-Reply-To: <494F0531-B180-4C08-B435-39CB3BCB5F3D@opscode.com>

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

All our chef scripts were written with ubuntu 10.04 in mind and we had not
correctly separated the os dependencies from the application deployment.
Then we had to deploy to Centos :)

So our chef scripts broke in all sorts of interesting ways. I don't ascribe
this to a problem with chef when it could so easily be our scripts being
badly written so don't worry about chef.

However we need to get runit working on Centos regardless so we have hacked
up some scripts to do this.

Runit installs fine, or at least without error but things are not working
out.

For instance there is no /etc/init.d/runsvdir or similar. The truth be told
there isn't one on Ubuntu either but some how Ubuntu is managing to start
up "runsvdir -P /etc/service" without any problem. So one question would be
how to get this to happen on Centos 5.8?

  reply	other threads:[~2013-05-09 13:03 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
2013-05-07 11:17   ` Peter Hickman
2013-05-07 17:47     ` Joshua Timberman
2013-05-09 13:03       ` Peter Hickman [this message]
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=CALxYQy4Kzb7LOza80icg1CBBeHan_DXPGne1JzPuqfT_3stB5g@mail.gmail.com \
    --to=peterhickman386@googlemail.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).