On Thu, Oct 15, 2009 at 3:49 PM, James Turnbull wrote:
>
> 2009/10/14 Paul Lathrop :
>> You misunderstand. Nigel and I are saying the generated config should
>> be known to *work*; it shouldn't have genconfig set to true in it. It
>> is counterintuitive for the output of --genconfig to be a confi
Thank you
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
puppet-users+unsubscr
there is also a param for service called "pattern" that allows you to
specify the regex that should be used to determine the process (in case one
of them doesnt properly implement status)
On Thu, Oct 15, 2009 at 8:53 PM, Matthias Saou <
th...@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrp
Douglas Garstang wrote:
[...]
> It seems to me like there might be a bug here. Puppet appears to think
> the syslog-ng and syslog service are the same thing and stops
> syslog-ng instead of syslog.
> If I change the name of the syslog service, like this...
>
> service { "XXXsyslog":
> e
I've got a host here where I am trying to ensure that syslog-ng is
running, and not surprisingly that syslog is NOT running.
My manifest has...
class syslog_ng {
package { "syslog-ng":
name => "syslog-ng",
ensure => installed;
}
service { "syslog":
ensure =>
On Thu, 15 Oct 2009 17:33:46 +0200
Bjørn Dyresen wrote:
>
> Best way to really find out, would be to try it out :)
Sure, but I was asking for other's experience/advices :-)
Anyway, thanks for your reply!
Arnau
--~--~-~--~~~---~--~~
You received this message be
Best way to really find out, would be to try it out :)
On Oct 15, 2009, at 3:51 PM, Arnau Bria wrote:
>
> Hi all,
>
> I'm not sure if next conf is going to work:
>
> I'd like to distribute a dir in recurse way, but then add a req on a
> certain file that is under that reurse dir.
>
> Example:
>
Paul Nasrat wrote:
> 2009/10/15 li...@truthisfreedom.org.uk :
>> Hi All,
>>
>> I notice from http://reductivelabs.com/trac/puppet/wiki/PuppetWindows
>> that puppet will be able to run on windows as of 0.26.0.
>>
>> The document only really talks about managing users, are there plans to
>> expand t
2009/10/15 Steven Jenkins :
>
> On Thu, Oct 15, 2009 at 9:36 AM, Paul Nasrat wrote:
> ...
>> I hope to mail the current patches to clean up core and a status
>> update to list on the weekend
>>
>
> Are there github repos that interested people could/should be tracking?
I need to push up tonight,
Hi all,
I'm not sure if next conf is going to work:
I'd like to distribute a dir in recurse way, but then add a req on a
certain file that is under that reurse dir.
Example:
file { "/opt/localconf":
ensure => directory,
owner
On Thu, Oct 15, 2009 at 9:36 AM, Paul Nasrat wrote:
...
> I hope to mail the current patches to clean up core and a status
> update to list on the weekend
>
Are there github repos that interested people could/should be tracking?
Thanks,
Steven
--~--~-~--~~~---~--~--
2009/10/15 li...@truthisfreedom.org.uk :
>
> Hi All,
>
> I notice from http://reductivelabs.com/trac/puppet/wiki/PuppetWindows
> that puppet will be able to run on windows as of 0.26.0.
>
> The document only really talks about managing users, are there plans to
> expand this to other things, or ar
Hi All,
I notice from http://reductivelabs.com/trac/puppet/wiki/PuppetWindows
that puppet will be able to run on windows as of 0.26.0.
The document only really talks about managing users, are there plans to
expand this to other things, or are there other functions that are
enabled already...o
Kim Gert Nielsen wrote:
> hmm then the debian version must be backported because it works in
> 0.24.5-3 :)
>
> On Oct 15, 2009, at 1:36 PM, Marc Fournier wrote:
>
>> Beware that distributing facts and libs in modules doesn't work from
>> environments before 0.25.
It may be more correct to sa
> hmm then the debian version must be backported because it works in
> 0.24.5-3 :)
it works if you define standard (non-per-environment) paths as well,
but puppet will then take the facts and plugins from this path and not
actually from the one in the environments.
cheers pete
--~--~---
hmm then the debian version must be backported because it works in
0.24.5-3 :)
On Oct 15, 2009, at 1:36 PM, Marc Fournier wrote:
>
>> but the other article is quite interesting because I
>> was going to use the enviroment for customers .. so instead of
>> development I would use customer01
>
> but the other article is quite interesting because I
> was going to use the enviroment for customers .. so instead of
> development I would use customer01
Beware that distributing facts and libs in modules doesn't work from
environments before 0.25.
Marc
--~--~-~--~~
no not really but I found the problem .. the version I have a bug when
using allow * in fileserver.conf and then I changed that to the IP it
worked :) but the other article is quite interesting because I was
going to use the enviroment for customers .. so instead of development
I would us
Douglas,
> I'm getting really really frustrated with puppet.
I also had a tough time configuring the client and the server part on
the same host.
I finally settled down to completely seperate the 2, by starting
puppetmaster with "--confdir=/etc/puppetmaster".
I then have a super simple puppetm
On Wed, 2009-10-14 at 15:19 -0700, Douglas Garstang wrote:
> Can someone tell me what this means? I am getting this in
> /var/log/puppet/masterhttp.log on the server.
>
> [2009-10-14 15:07:35] DEBUG accept: 10.10.1.23:33626
> [2009-10-14 15:07:35] ERROR `/production/certificate/ca' not found.
> [
20 matches
Mail list logo