Hi,
I'm a newb to puppet but have a good deal of experience with
CFEngine. We want to replace CFEngine in our environment because of
its monolithic nature. As a proof of concept, I'd like to duplicate a
particular function we've always had trouble with in CFEngine -
installing HP PSP on our Redh
You are a genius! Thank you very much :D
Best Regards,
Michael Schenck
On Oct 31, 12:52 pm, RijilV <[EMAIL PROTECTED]> wrote:
> 2008/10/31 tek-ops <[EMAIL PROTECTED]>:
>
>
>
> > What would really help is if there was a node definition like
> > "default" that was used by all nodes, not just ones
2008/10/31 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> Hi, I'm new to puppet.
> here's my config:
>
> define touchfile {
> exec { "/usr/bin/touch $title": }
> }
>
> file { "/etc/host.conf":
> notify => touchfile["/var/tmp/touchfile.txt"],
> }
>
so I think you're using defines like functions, wh
Hi, I'm new to puppet.
here's my config:
define touchfile {
exec { "/usr/bin/touch $title": }
}
file { "/etc/host.conf":
notify => touchfile["/var/tmp/touchfile.txt"],
}
What I expect: wenn I modify my host.conf, the touchfile.txt is
touched. But it doesn't work that way. What I get is:
Oct
2008/10/31 tek-ops <[EMAIL PROTECTED]>:
>
> What would really help is if there was a node definition like
> "default" that was used by all nodes, not just ones that are otherwise
> not defined. Although this "may" have the same scope issue of
> resolving this with a class.
>
does the below not
What would really help is if there was a node definition like
"default" that was used by all nodes, not just ones that are otherwise
not defined. Although this "may" have the same scope issue of
resolving this with a class.
On Oct 30, 5:46 pm, tek-ops <[EMAIL PROTECTED]> wrote:
> I'm attempting
Ben wrote:
> Bryan Kearney wrote:
>> David Lutterkort wrote:
>>
>>> On Mon, 2008-09-08 at 10:49 -0400, Bryan Kearney wrote:
>>>
David Lutterkort wrote:
> Yeah, Augeas should be able to tell the caller whether changes were made
> or not, so that the plugin can suppr
On Thu, Oct 30, 2008 at 6:12 PM, Andrew Shafer <[EMAIL PROTECTED]>wrote:
> Arnau,
Hi Andrew,
>
> The groupinstall is specific behavior to yum, it isn't an abstraction
> supported by Package resource.
Yep,
*yum*: Support via yum. Required binaries: python, rpm, yum. Default for
operatingsystem
On Thu, Oct 30, 2008 at 5:39 PM, RijilV <[EMAIL PROTECTED]> wrote:
> > So, I'm not using "package" here, I'm doing it with exec, telling that if
> > the package is foobar, execute "yum groupinstall"... but then, it will be
> > logged out of package type section... is it?
>
> Honestly I wouldn't u
This only happens on one file, right?
Unless I'm reading the stack and the code wrong, I suspect there is
something corrupted in the yaml cache for the md5.
Let's try removing that and see if it works. Don't just delete it though,
send it to the list and let's see if there is some forensic value
10 matches
Mail list logo
