Really? I use it all the time with Solaris - it works just fine.
Op dinsdag 12 maart 2013 11:52:37 UTC+1 schreef Rajeev Iyer het volgende:
>
> Too many issues when it comes to Solaris installation. So moving to Chef..
>
> Thanks all..
>
--
You received this message because you are subscribed
On Wednesday, May 16, 2012 4:20:23 PM UTC+2, Alex Harvey wrote:
>
> Thanks kindly to all for the thoughtful responses. I'll be looking
> closely at the idea of using load balanced Puppet servers.
>
> I wonder if anyone has any thoughts on the other problem I'm told I'll
> probably encounter, n
Sounds good.
One problem that I have with the forge is that the extent to which the
modules have been tested is not clear to me. Can I take it that the core
modules that ship with puppet will have been through a similar testing
cycle as puppet itself?
On Monday, April 23, 2012 11:03:39 PM UT
I didn't realise that would work.
Here's a trivial tested example derived from Felix's comment:
class mod::class($param1, $param2) {
file {"$param1/$param2": content => "Bla\n"}
}
class mod::class::sub1 inherits mod::class {
File["$param1/$param2"] {content => "Sub1\n"}
}
And then in th
You can only inherit from a parameterised class if you provide
defaults for all of the parameters (and then of course those are the
values that are used).
What you could do is just have a single class with something like a
type parameter. Then your class would have something like:
if $type == "lo
You need to use the adminfile and source parameters - once you have
done that the provider works just fine.
On Dec 28, 4:19 pm, Peter Berghold wrote:
> Hi folks,
>
> I'm about to propose to my current company that we use puppet to manage
> releases of home grown software. The environment is a mi
The following would work:
node default {
class { sudoers: }
}
node 'sl11lab02' {
class { sudoers: additional_rules => [ "$rules_uas" ] }
}
On Mar 18, 12:03 am, Ashley Gould wrote:
> I am exploring usage of parameterized classes. I hit a wall when
> trying to override values of paramet
uglas Garstang wrote:
> On Sun, Mar 6, 2011 at 2:48 AM, Bill Proud wrote:
> > SSL_write is the function that writes to an SSL connection. Evidently
> > in this case there was an error - perhaps the connection was lost.
>
> This error is occurring on multiple clients at regular
SSL_write is the function that writes to an SSL connection. Evidently
in this case there was an error - perhaps the connection was lost.
Bill
> Okidoki. below is what appeared in the masterhttp.log file when this
> client tried to connect.
>
> [2011-03-06 06:46:34] ERROR OpenSSL::SSL::SSLEr
Sorry Jed I didn't realise that you didn't know about .puppet
directories. A .puppet directory is created in your home directory if
you accidentally run puppet as yourself and not as root. The problem
that I had was that sometimes puppetd was correctly reading SSL
settings from /var/lib/puppet/ss
What I find works is a configuration along the following lines:
node mirror {
$my_role = "mirror"
}
node 'mirror.example.com' inherits mirror {
include iptables
include basenode
include sendmail
include sshkeys
}
--
You received this message because you are s
I also had an intermittent error like this. If I looked in the
puppetmaster http log I saw that there were SSL errors on some runs
but not on all.
In the end I found that removing a .puppet directory that I had
inadvertently created solved my problem.
On Jan 5, 12:29 am, joe wrote:
> I have the
On Dec 20, 7:57 pm, Nick Moffitt wrote:
> I'd like to know the best way to fix the refresh/restart behavior of
> Service resources without using ensure => running.
>
> I know that this is an unpopular requirement, but I do not want puppet
> to restart dying services before my monitoring system not
er than doing a checkout you will
not get the .svn directories.
Bill Proud
--
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
The following would work:
class a {
if $x { notify "yeah!" }
}
node base {
$x = true
}
node test inherits base {
include a
}
On Nov 29, 12:21 pm, walexey wrote:
> puppet 2.6.3
>
> How i can make this work?
>
> class a {
> if ($b::x) { notify "yeah!" }
>
> }
>
> class b {
> $x=tr
Hi,
If you nest classes like that then you probably do have to dump
everything in init.pp
If however you split the classes and define each in a separate file
with the name .pp in the manifests directory of the module, you
will be able to "include m_feature::specialized".
No problem with the inhe
16 matches
Mail list logo
