i see... i'll give it a shot .
Thanks for the input.
chakkerz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe f
Ohad Levy wrote:
> Most segfaults are due to old version of ruby... I assume that if you
> upgrade your ruby everything should work as expected...
I was able to get past the segfault by putting in
libshadow-ruby1.8_1.4.1-8_i386.deb; I had to force it though (it wanted
a newer libc6), so I su
Most segfaults are due to old version of ruby... I assume that if you
upgrade your ruby everything should work as expected...
Cheers,
Ohad
On Thu, Feb 26, 2009 at 12:47 AM, Kyle Cordes wrote:
>
>
> Trying to fire up Puppet 0.24.7 on an Ubuntu 6.06 x64 machine (yes, I
> know it's obsolete, but
> More troubleshooting with various debug options revealed that if I specified
> --onetime to puppetd, it performed a normal run as expected. If, however, I
> start it up as normal - exactly the same, except without onetime - the client
> just hangs.
Just as a followup to anyone who hits the
On Wed, Feb 25, 2009 at 2:08 PM, Scott Beardsley
wrote:
> BTW, I noticed that .svn directories were being copied to
> /var/lib/puppet. Here is a trivial patch to prevent that behavior...
>
> $ diff /tmp/init.pp modules/shorewall/manifests/init.pp
> 65a66
>> ignore => ".svn"
BTW, I noticed that .svn directories were being copied to
/var/lib/puppet. Here is a trivial patch to prevent that behavior...
$ diff /tmp/init.pp modules/shorewall/manifests/init.pp
65a66
> ignore => ".svn"
--~--~-~--~~~---~--~~
You received
AHH HA! I got busy but I just now took another look at this and have
solved my problem. I fixed it by changing the node definition as
follows:
node 'foo.com' {
include shorewall::debian
}
to:
node 'foo.com' {
include shorewall
}
I wasn't creating an instance of the shorewall cl
Trying to fire up Puppet 0.24.7 on an Ubuntu 6.06 x64 machine (yes, I
know it's obsolete, but we have a pile of machines), I get this failure:
# /etc/init.d/puppet start
* Starting puppet configuration management tool
/usr/lib/ruby/1.8/x86_64-linux/shadow.so:
> but I think a bug with the redhat provider
you're right.
I verified it and filed a bug: http://projects.reductivelabs.com/issues/2026
So wen can track it.
cheers Pete
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
the asterisks was comming because I have write in html and put theses line
on bold :(
Vincent
On Wed, Feb 25, 2009 at 1:03 PM, Bruce Richardson wrote:
>
> On Wed, Feb 25, 2009 at 12:52:29PM +0100, Vincent Louviaux wrote:
> > Hello,
> >
> > I am trying to disable a process , but the stop paramete
Ok I have add
provider=>"base",
Thanks for the tips !
but I think a bug with the redhat provider
Vincent
On Wed, Feb 25, 2009 at 1:11 PM, Trevor Vaughan wrote:
>
> I ran into this problem as well.
>
> I ended up having to set my 'provider' to 'base' and then specify
> everything manually.
>
>
All,
Are regexes supported in if/else statements?
For example:
if $foo =~ /^some.*string$/ {
notice ("I foo'd")
}
else {
notice ("bar")
}
If not, are there any plans to do so?
(Yes, I know I need to stop asking questions and start submitting patches :-/)
Caveat: I haven't been able to u
I ran into this problem as well.
I ended up having to set my 'provider' to 'base' and then specify
everything manually.
Trevor
On Wed, Feb 25, 2009 at 06:52, Vincent Louviaux wrote:
> Hello,
>
> I am trying to disable a process , but the stop parameter seems to be
> ignored
> from the output o
On Wed, Feb 25, 2009 at 12:52:29PM +0100, Vincent Louviaux wrote:
> Hello,
>
> I am trying to disable a process , but the stop parameter seems to be
> ignored
> from the output of puppetd -tv :
> ..
> err: /:main/sastools/Service[cfexecd]/ensure: change from running to stopped
> failed: Execution
Hello,
I am trying to disable a process , but the stop parameter seems to be
ignored
from the output of puppetd -tv :
..
err: /:main/sastools/Service[cfexecd]/ensure: change from running to stopped
failed: Execution of '*/sbin/service cfexecd stop*' returned 1: cfexecd:
unrecognized service
..
fr
15 matches
Mail list logo
