Re: [Puppet Users] Determining the syslog provider

2012-06-14 Thread David Schmitt
On 12.06.2012 14:45, Julien C. wrote: Thanks to both of you for your answers. I am aware of the operatingsystem and release variables, but I can't rely on them because servers don't always use the default syslog provider, as stated in my original post. I can't enforce the same provider on every n

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Ramin K
On 6/12/2012 2:39 PM, Julien Cornuwel wrote: I think you are right (all three of you). I need to find out how to find it in other OS families (debian & redhat should be enough) and write a custom fact to get the data in my manifests. Thanks for the pointers. The downside to a custom fact is th

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Julien Cornuwel
I think you are right (all three of you). I need to find out how to find it in other OS families (debian & redhat should be enough) and write a custom fact to get the data in my manifests. Thanks for the pointers. 2012/6/12 Alex : > Would a custom fact work in this case?  I am not a ruby coder, bu

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Alex
On 06/12/2012 02:45 PM, Julien C. wrote: Thanks to both of you for your answers. I am aware of the operatingsystem and release variables, but I can't rely on them because servers don't always use the default syslog provider, as stated in my original post. I can't enforce the same provider on ev

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Felix Frank
On 06/12/2012 02:45 PM, Julien C. wrote: > > I need to know which is the running logger and add my configuration in > its config files. > The first step to do this is to identify it, hence this post's title. Huh, well the most canon apprach is custom facts: http://docs.puppetlabs.com/guides/custo

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Darin Perusich
On SuSE systems the init script determines which syslog daemon by the value of SYSLOG_DAEMON in /etc/sysconfig/syslog, the values can be "syslogd", "syslog-ng", "rsyslogd" or "" for autodetect. You should be able to leverage those to determine which logger to use. -- Later, Darin On Tue, Jun 12,

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Julien C.
Thanks to both of you for your answers. I am aware of the operatingsystem and release variables, but I can't rely on them because servers don't always use the default syslog provider, as stated in my original post. I can't enforce the same provider on every node because it would destroy any cus

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread maillists0
On Tue, Jun 12, 2012 at 8:12 AM, Julien C. wrote: > Hi, > > I'm trying to make all my servers send their logs to a central server. Which > seems quite simple, at first. > > My problem is that my servers are on different versions of different > operating systems. > And each of them has a different

Re: [Puppet Users] Determining the syslog provider

2012-06-12 Thread Felix Frank
Hi, On 06/12/2012 02:12 PM, Julien C. wrote: > Hi, > > I'm trying to make all my servers send their logs to a central server. > Which seems quite simple, at first. > > My problem is that my servers are on different versions of different > operating systems. > And each of them has a different sys

[Puppet Users] Determining the syslog provider

2012-06-12 Thread Julien C.
Hi, I'm trying to make all my servers send their logs to a central server. Which seems quite simple, at first. My problem is that my servers are on different versions of different operating systems. And each of them has a different syslog default provider (syslog, rsyslog, syslog-ng...). Which