From: Peter Hickman <peterhickman386@googlemail.com>
To: supervision@list.skarnet.org
Subject: Re: Installing on Centos
Date: Tue, 7 May 2013 12:17:50 +0100 [thread overview]
Message-ID: <CALxYQy7REfagtpjhLNaOg7Pbnkv2c5=mt7x_xZwdLNfgzzazbg@mail.gmail.com> (raw)
In-Reply-To: <20130507105625.GA2125@home.power>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
Thanks that a place to start at least. The problem for me is that all our
previous installs were from a chef script and things just magically worked.
The scripts borked on Centos and I have to try and work out how the working
system got tat way.
next prev parent reply other threads:[~2013-05-07 11:17 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 [this message]
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='CALxYQy7REfagtpjhLNaOg7Pbnkv2c5=mt7x_xZwdLNfgzzazbg@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).