See the 'recurse' and 'purge' parameters of the file type.
http://docs.puppetlabs.com/references/latest/type.html#file
file{'/root/mydir':
ensure => directory,
recurse => true,
purge => true,
}
file{['/root/mydir/a','/root/mydir/b','/root/mydir/c
Hi,
I need to manage some files in a directory. Lets say, /root/mydir can
contain only file a,b & c and rest others should be discarded. How can I
maintain it with Puppet code?
Thanks,
amogh
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
Hi,
sure. From puppet apply --help
"""
* --logdest:
Where to send messages. Choose between syslog, the console, and a log
file. Defaults to sending messages to the console.
"""
So you can either use --logdest=syslog or add logdest=syslog to the
appropriate sections of puppet.conf.
HTH,
Felix
Thanks for the lengthy explanation. I suppose that, for one thing, I
didn't understand the algorithm that was used in puppetcommander. The
one thing that will complicate this for me is my horribly poor ruby
skills, coupled with the fact that the MCo python bindings appear to be
abandoned (though I
- Original Message -
> From: "Jose Luis Ledesma"
> To: puppet-users@googlegroups.com
> Sent: Tuesday, December 31, 2013 4:51:04 PM
> Subject: Re: [Puppet Users] MCollective/Puppet - one-time run with other
> options
>
> The problem about using runall/concurrency is that you cannot know
The problem about using runall/concurrency is that you cannot know when it will
finish, so setting it on the crontab could be a source of a problems if it has
not yet finished when the next run is schedulee
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
Our site has several dozen yum repositories. Pushing all yum repositories to
all servers isn't practical; it hurts performance, some repositories are
OS-specific, and some repositories cause conflicts with each other (we have a
ruby187 repo and a ruby 193 repo, for example).
In our current setu
- Original Message -
> From: "Jason Antman"
> To: puppet-users@googlegroups.com
> Sent: Tuesday, December 31, 2013 4:33:43 PM
> Subject: Re: [Puppet Users] MCollective/Puppet - one-time run with other
> options
>
> Christian - we don't use puppet just to "make changes", we use it as
>
What do you mean by balancing nodes?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the we
Christian - we don't use puppet just to "make changes", we use it as
(IMO) it was intended - to prevent divergence. We want it running every
30 minutes to make sure things stay how the manifests/modules say.
Jose - I think that may be the way I go, but I'm going to see if I can
get something (perh
Great Jason - I'll take a look (have done a ton of Python.)
Happy new year.
On Dec 31, 2013, at 4:06 AM, Jason Antman wrote:
> Stuart,
>
> I know this took a while, but there were some bureaucratic hoops to be jumped
> through first.
>
> Our Python/Django (Postgres-backed) ENC, or what exis
Hi,
At my work place we have puppet stopped completely. We only run it via
mco when we update the manifests. But this implies that you don't use
exported resources.
regards,
Cristian Falcas
On Tue, Dec 31, 2013 at 3:32 PM, Jose Luis Ledesma
wrote:
> Hello,
>
>We have puppet only in the lab'
http://stackoverflow.com/a/20856330/1242724
m.
On Tuesday, June 24, 2008 2:34:22 PM UTC+2, Thomas Bellman wrote:
>
> I have a few ERB templates that have some common parts, and I
> want to break out those parts into a separate file that I can
> just "include" in the main templates. If this inclu
On 12/31/2013 04:16 AM, Steph Gosling wrote:
Isn't it!
Applying that resource fails in the same way: as requested here's the
output though debugging doesn't seem to add anything, which is a bit odd.
[root@nodename steph]# puppet apply --debug --verbose -e 'file {
"/tmp/test": ensure => link,
Hello,
We have puppet only in the lab's servers, we are planning to deploy to
production in the near future. I found myself thinking about the same
question some time ago.
What we were thinking is, why to run puppet agent on every node? In fact
puppetlabs says about setting the puppet ag
I corrected the problem by including this in my /etc/init.d/
I also forgot the scariest option, which seems apt to break things:
- have mcollective stop the daemon
- mco puppet runonce
- have mcollective start the daemon back up
-jason
On 12/31/2013 07:42 AM, Jason Antman wrote:
> Hello,
>
> I've recently learned that my plans to use the puppet agent mcoll
Hello,
I've recently learned that my plans to use the puppet agent mcollective
plugin to trigger one-time runs against a different environment, with
the daemon running in the background, don't work because of how the
agent plugin works (SIGUSR1 to the daemon if running).
My original intent was as
Stuart,
I know this took a while, but there were some bureaucratic hoops to be
jumped through first.
Our Python/Django (Postgres-backed) ENC, or what exists of it so far, is
now at https://github.com/coxmediagroup/nodemeister
Be advised this is horribly Alpha, doesn't really have any tests yet,
Hi Felix,
Sorry for delay in responding!
Thanks, I am using red hat platform and logs are created as redirected
output of console to a file on puppet run.
Once again thanks for your input, Could you please point out a sample to
use syslog ?
Regards,
Jay
Regards,
Jay
On Sun, Dec 22, 2013 at
Isn't it!
Applying that resource fails in the same way: as requested here's the
output though debugging doesn't seem to add anything, which is a bit odd.
[root@nodename steph]# puppet apply --debug --verbose -e 'file {
"/tmp/test": ensure => link, target =>
"/tmp/test-target" }'
Info: Loading f
Hi everybody,
is there any news about this topic?
I think it would be great to know Puppetlabs' official position on the
matter (if any), and the status of activities about it (issues on
tickets.puppetlabs.com don't say much).
Thanks!
--
You received this message because you are subscribed to
22 matches
Mail list logo
