Paul Gear wrote:
> David Schmitt wrote:
>> ...
>>> I'd rather not distribute the entire directory from the server, since it
>>> contains custom content for each node. Is there a way i can do this
>>> with templates that include other files? (Or templates that are plain
>>> text rather than .erb?
niczar wrote:
> I can't figure how to do this cleanly, here's the story:
>
> I have an rsyslog class with a template generating /etc/rsyslog.conf
>
> I have some other classes (namely, ossec::server, does what it says)
> that need to influence what's going on inside rsyslog.conf, in
> particular
I'm not sure I understand. Do you mean create a new database?
Ciao,
Sheldon.
--~--~-~--~~~---~--~~
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
I love where this thread is going, I too share in this problem.
Kurt: Puppet is still being run on the client because the client is
using a cached config (am I right on this guys?).
I love the scripted ssh key, but ALSO love the PHP script that could
be CURL-ed from the client. Will a PHP scri
Gary Larizza wrote:
> I love where this thread is going, I too share in this problem.
>
> Kurt: Puppet is still being run on the client because the client is
> using a cached config (am I right on this guys?).
>
> I love the scripted ssh key, but ALSO love the PHP script that could
> be CURL-ed
FYI puppetd --test or puppetd -t is shorter than all of that
--one-time --no-daemonize etc stuff and is basically the same.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group,
Hi Curt,
Did you manage to resolve this issue? If not I think it may be the
format of your yaml output.
>---
>classes:
>- custom
>- monitoring::base
Should be this
---
classes:
- custom
- monitoring::base
Note the indentation. Having said that I have been unable to persuade
the python y
I also turn on reporting back to puppetmaster via --report and have
found that very useful for debugging and figuring out state centrally.
On 7/3/09, Sam Rowe wrote:
>
> FYI puppetd --test or puppetd -t is shorter than all of that
> --one-time --no-daemonize etc stuff and is basically the same.
I am currently working on doing a very similar thing with kickstart.
There are two ways you can deal with the hostname... have PHP do an
nslookup for the ipaddress that is connecting (prefered for security
reasons), or just pass it as an argument to the PHP script.
Chris
On Jul 3, 2009, at
On Jul 3, 12:51 pm, Christopher Webber wrote:
> I am currently working on doing a very similar thing with kickstart.
> There are two ways you can deal with the hostname... have PHP do an
> nslookup for the ipaddress that is connecting (prefered for security
> reasons), or just pass it as
On Fri, Jul 3, 2009 at 12:05 PM, Martin Wheldon wrote:
>
> Hi Curt,
>
> Did you manage to resolve this issue? If not I think it may be the
> format of your yaml output.
>
>>---
>>classes:
>>- custom
>>- monitoring::base
>
> Should be this
>
> ---
> classes:
> - custom
> - monitoring::base
>
>
On Jul 3, 12:38 am, Allan Marcus wrote:
> Can you create fact that determines your condition (if ossec server is
> to be or is installed I take it)? You can then refer to the fact in
> your rsyslog code.
Hm, no, whether or not ossec::server is installed is decided in my
puppet config file,
On Jul 3, 9:56 am, David Schmitt wrote:
> The rsyslog class needs to setup a way to include "foreign"
> configuration statements, like by using a directory include or a
> concatenated_file. Then any other class can put configuration there and
> rsyslog will pick it up easily.
What is a concat
here you go, its fetched from a much bigger website, so I didnt really test
it, but worth a shot :)
http://gist.github.com/140457
cheers,
Ohad
On Fri, Jul 3, 2009 at 9:12 PM, Gary Larizza wrote:
>
> I love where this thread is going, I too share in this problem.
>
> Kurt: Puppet is still bein
14 matches
Mail list logo