We use it on our RHEL3 boxes and the other poster is correct. You must
build all the dependencies yourself. Fortunately for use we have a build
environment for it still and it hasn't been an issue.Once you get through
that though, it works remarkably well.
Drew
On Mon, Jun 7, 2010 at 1:56 PM, D
y straight-forward? If not, mind sharing your
> changes/spec files/rpm's?
>
> Thanks,
> Dan
>
>
> On Jun 7, 2010, at 3:03 PM, Andrew Hamilton wrote:
>
> We use it on our RHEL3 boxes and the other poster is correct. You must
> build all the dependencies yourself.
I have a question hopefully someone here can help me out with. I have a
module that I didn't write, I got it from the github. it's the postgres
module. I'm running on CentOS 5. In the module there is this:
case $ensure {
present: {
exec { "Create $name postgres db":
Thanks for the replies and other possibilities. I'm using version 0.25.2 of
puppet. I did a different kind of workaround mostly by doing the same thing
with a straight psql command with no pipe. ie.
"/usr/bin/psql -c 'select * from pg_user where usename = 'myuser'"
This at least seems to not e
xing...
Thanks,
Drew
On Thu, Feb 25, 2010 at 9:21 AM, Andrew Hamilton wrote:
> Thanks for the replies and other possibilities. I'm using version 0.25.2
> of puppet. I did a different kind of workaround mostly by doing the same
> thing with a straight psql command with no pipe. ie.
e return value of my command is 0 then the command
will not run, yet I can verify that the return value of the command is 0,
yet it still runs. Unless I have this backwards and my interpretations are
incorrect.
Thanks,
Drew
On Thu, Feb 25, 2010 at 10:01 AM, Andrew Hamilton wrote:
> This
g along since though.
Drew
On Wed, Mar 3, 2010 at 5:11 AM, Michael Gliwinski <
michael.gliwin...@henderson-group.com> wrote:
> On Friday 26 Feb 2010 16:03:41 Andrew Hamilton wrote:
> > I can't thank you enough. This worked perfectly for me. I don't know
> how
> &g
