I am trying to make use of a custom type mentioned in the wiki page
http://projects.puppetlabs.com/projects/1/wiki/Sysctl_Patterns
I created the module sysctl, inserted the custom type in there and
created a simple manifest to make use of the introduced type.
I add the module to a client and star
nced there. Then
> try your client again.
>
> The problem is your server isn't scanning your modulepath for types
> ... its expecting types to be in its own libdir first. Hence why an
> pluginsync is needed ...
>
> ken.
>
> On Thu, Jul 7, 2011 at 12:18 PM, JohnW wro
Hello
I have been using puppet for a while now, more or less successfully on
SLES 11 and CentOS 5.5
currently I am using puppet 2.6.6
I now am trying it out on redhat 6, and now i run into an problem with
even the simplest of modules/classes
The error I get is :
debug: /Stage[main]/Motd/File[/e
les are used without problems on systems with SLES11 and
CentOS 5.5
- John
On Apr 1, 9:36 pm, Frank Sweetser wrote:
> On 4/1/2011 5:15 AM, JohnW wrote:
>
>
>
> > Hello
>
> > I have been using puppet for a while now, more or less successfully on
> > SLES 11 and
:
> On Apr 4, 3:45 am, JohnW wrote:
>
> > info: Applying configuration version '1301906526'
> > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
> > yaml; using pson
> > debug: /File[/etc/issue.net]/content: Executing 'diff -u /etc/
Hello,
Does anyone have a good spec file for puppet dashboard 1.1.0, as the
one supplied in the sourcecode is for 1.0.4
and tries to copy some directories, that don't exist anymore.
I did some remodelling in the file, so it creates a rpm now, but I'm
not sure whether my "fix" is the only change
Hello,
I'm using the following call in my default profile:
notify { "development":
message => "Puppet environment development",
loglevel => " info";
}
with similar entries in other environments.
This works as expected with one exception, the way
