[Puppet Users] Re: Influencing a class from another one?

[Jim Pirzyk]

Other solution would be to create a rsyslog type and call it in the ossec::server class.

I have a sendmail class that has this syslog type:

        syslog { "/var/log/maillog":
                selector => "mail.debug",
                ensure => present,
                owner => root,
                group => mail,
                mode => 644,
        }



- JimP

On Jul 2, 2009, at 6:38 PM, Allan Marcus wrote:

I have a rsyslog provider that knows how to format this data into the proper /etc/rsyslog.conf syntax.

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.

---
Thanks,

Allan Marcus
505-667-5666



On Jul 2, 2009, at 3:03 PM, 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 want local0.* not to be logged in /var/log/messages on
the machines that include ossec::server

How can I do that? I can't seem to be able to do it with variables.

Any help appreciated.

--~--~---------~--~----~------------~-------~--~----~

To post to this group, send email to puppet-users@googlegroups.com

You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group, send email to puppet-users +unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/ group/puppet-users?hl=en

-~----------~----~----~----~------~----~------~--~---

--- @(#) $Id: dot.signature,v 1.15 2007/12/27 15:06:13 pirzyk Exp $
    __o  j...@pirzyk.org -------------------------------------------
 _'\<,_
(*)/ (*) I'd rather be out biking.

PGP.sig
Description: This is a digitally signed message part