Boa noite pessoal,
Estou criando um modulo para a instalação e configuração dos backups com o
bacula.
A estrutura do meu módlo inicial é:
director.pp
storage.pp
client.pp
console.pp
init.pp
O problema que as 4 primeiras classes usam na sua configuração campos
iguais, porém em arquivos diferente
Hi Chris,
So glad you asked.
Try https://github.com/NationalSecurityAgency/SIMP for the 'official'
overview and https://simp-project.com for the more visually appealing
version.
Thanks,
Trevor
On Fri, Mar 3, 2017 at 1:09 PM, Chris S. wrote:
> Hello all,
>
> Does anyone have a good method to
Hello all,
Does anyone have a good method to Adhere to the RHEL STIG or even CIS
benchmark usign Puppet. I'm inclined to write some of my own modules
and/or use some from the forge to piecemeal a solution. I was wondering is
anyone has an Approved or Supported all encompassing solution to th
On Wed, Mar 1, 2017 at 6:50 PM, Adam Mercer wrote:
> Error: Facter: error while processing
> "/opt/puppetlabs/facter/facts.d/packages.json" for external facts: The
> document is empty.
I have now started seeing this on both Debian 8 and Ubuntu 16.04. Any
ideas where to start debugging this?
Che
Excellent, this is exactly what I was hoping for. Thanks.
On Friday, March 3, 2017 at 10:30:42 AM UTC-7, Peter Kristolaitis wrote:
>
> A subscribed / notified resource will only trigger once. Puppet's basic
> execution model only allows each resource to run once during a catalog run,
> and you
A subscribed / notified resource will only trigger once. Puppet's basic
execution model only allows each resource to run once during a catalog
run, and you can think of notify/subscribe as a special case of using
'require' to determine execution order.
On 3/3/2017 12:14 PM, Joshua Schaeffer
Ahoy all,
TL;DR
I'm looking for information on how a catalog runs, in particular if you
notify an exec resource within a manifest multiple times (from different
resources) will the exec run multiple times if it has refreshonly set to
true? I've given more details below:
Background information
This would be the ideal but you *can* use the rpm provider when needed.
For example:
package { 'jdk':
ensure => installed,
provider => 'rpm',
source => '/pub/oracle/jdk-8-linux-x64.rpm',
}
This will install the rpm using the defined source path. In our
environment the /pub dire
Also, it looks like somebody tried to fix this previously but the changes
weren't merged in.
See https://github.com/voxpupuli/puppet-nginx/issues/333 for example. IMO
there should be a class parameter to control this behavior so you might
want to submit a PR with any changes you make.
On Fr
notify events are queued and grouped together so nginx should only be
restarted once when puppet runs. You may also need to include nginx in
your profile so that the service is properly defined.
On Friday, March 3, 2017 at 7:00:36 AM UTC-5, Steve Button wrote:
>
> Hi,
>
> I've got a small piec
Hi,
I've got a small piece of puppet in my profile module to remove the default
nginx.conf file which gets installed by the nginx module.
# Upon install this file gets created and displays "Welcome to NginX" page,
which we don't need.
file { '/etc/nginx/conf.d/default.conf':
ensure => 'abse
11 matches
Mail list logo
