Did anyone ever post a bug, or find a solution for this? I've just upgraded
some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm seeing the same
behaviour.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the w
Perfect - that's exactly what I needed. Thanks!
Chris
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@
Hi all,
I've recently started using "puppetmasterd --compile" to validate changes to
my manifests before I push them out onto the puppetmaster, which is a great
help in spotting syntax errors, missing resources and the like.
However, something I'd really like to be able to do, is to make a chan
On Fri, Nov 19, 2010 at 11:01 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 11/19/2010 10:56 AM, Chris May wrote:
> >
> > Thinking back to the original PSON bug, the workaround back then was
> > to use YAML serialization. I did notice t
>
>
> Thinking back to the original PSON bug, the workaround back then was to use
> YAML serialization. I did notice that that could make clients crash though,
> I think the 0.25.5 were the afflicted ones.
>
> You may want to give it shot though, anyway. The YAML encoder seems to be
> less picky wh
Hi Nan,
On Wed, Nov 17, 2010 at 12:12 AM, Nan Liu wrote:
> On Mon, Nov 15, 2010 at 7:38 AM, Chris wrote:
> > So; on to the question: Can I stop 0.24 clients from printing out file
> > contents when taking to a 2.6 master ? It's a bit of a security issue
> > when the files contain passwords or o
On Wed, Nov 10, 2010 at 6:26 PM, Richard Crowley wrote:
> > got the point, thought that you need one specific key on each server. So
> > that should be even simpler, use file with content and put the key in the
> > content field:
> >
> > $myKey = "-BEGIN RSA PRIVATE
> >
> KEY-\nMIICXgIBAA
