similar to: Fact based variables sowing up empty

On March 1, 2015 10:26:40 AM Reindl Harald <h.reindl at thelounge.net> wrote: > i guess for a C-programmer it takes not much more than 10 minutens > include a config option to list rbl servers and close connections absed > on the DNS responses close pop3, set imap to listen only in lo interface, setup webmail with smtp auth, now then in apache install mod geoip, and only allow

On 03/01/2015 04:25 AM, Reindl Harald wrote: >> I wonder if there is an easy way to provide dovecot a flat text >> file of ipv4 #'s which should be ignored or dropped? >> >> I have accumulated 45,000+ IPs which routinely try dictionary >> and 12345678 password attempts. The file is too big to create >> firewall drops, and I don't want to compile with

Hi, Before I begin, my environment consists of a standard master/client config with the exception that all my clients run under a non-root user. I have to use non-root so I can''t simply restart under root to fix the problem. Master -> 3.1.1 Client -> 2.7.17 using mostly the hiera() function in my classes. problem: I have run into an issue today where my custom fact is not

Team, I am trying to setup new Puppet master server on Centos 5.4. I am getting the below error which running yum install puppet-server puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems --> Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems --> Missing

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

ok after fighting to get my groups sorted out for my test user I created an "sudoer" group and added "jefftest" to "sudoer" > id jefftest uid=11507(jefftest) gid=8513(domain users) groups=8513(domain users),31020(sudoer) and added "sudoer" to /etc/sudoers like so %sudoer ALL=(ALL) ALL now when I login as jefftest I can run commands using sudo back to

I wonder if there is an easy way to provide dovecot a flat text file of ipv4 #'s which should be ignored or dropped? I have accumulated 45,000+ IPs which routinely try dictionary and 12345678 password attempts. The file is too big to create firewall drops, and I don't want to compile with wrappers *if* dovecot has an easy ability to do this. If dovecot could parse a flat text file of

Am 01.03.2015 um 08:53 schrieb Jim Pazarena: > I wonder if there is an easy way to provide dovecot a flat text file of > ipv4 #'s which should be ignored or dropped? > > I have accumulated 45,000+ IPs which routinely try dictionary and > 12345678 password attempts. The file is too big to create firewall > drops, and I don't want to compile with wrappers *if* dovecot has

Am 01.03.2015 um 23:16 schrieb Dave McGuire: > On 03/01/2015 04:25 AM, Reindl Harald wrote: >>> I wonder if there is an easy way to provide dovecot a flat text >>> file of ipv4 #'s which should be ignored or dropped? >>> >>> I have accumulated 45,000+ IPs which routinely try dictionary >>> and 12345678 password attempts. The file is too big to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list! In an effort to get feedback and spread the word, here follows the second article about possibilities to structure manifests. These Design Patterns are more general than the typical Puppet Recipie and will receive a own page on the wiki when I collect enough[1] material. To the meat: humane class names with namespaces Class names

I did gathered aggregate statistics reported by “-stats” over the ~400 test files. The following table summarizes the impact. The first column is the sum where the new analysis is enabled, the second column is the delta from baseline where no CFL alias analysis is performed. I am not experienced enough to know which of these are “good” or “bad” indicators. —david 72,250 685 SLP

trying to deploy puppetdb , puppet server is RHEL 6.1 , [root@puppet ~]# rpm -qa|grep puppet puppetdb-0.9.1-2.el6.noarch puppet-dashboard-1.2.9-1.el6.noarch puppet-server-2.7.17-1.el6.noarch puppetdb-terminus-0.9.1-2.el6.noarch puppet-2.7.17-1.el6.noarch on the clients, got an error for puppetdb , client1 :~ # puppet agent --test err: Could not retrieve catalog from remote server: Error 400

(and sys::cas_flag that STATISTIC uses is a uint32 ...) On Thu, Aug 25, 2016 at 9:54 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > Okay, dumb question: > Are you really getting negative numbers in the second column? > > 526,766 -136 mem2reg # PHI nodes inserted > > http://llvm.org/docs/doxygen/html/PromoteMemoryToRegister_8cpp_source.html >

The following function is based on code I found here in an earlier thread. define sudoer() { augeas { "sudo${name}": context => "/files/etc/sudoers", changes => [ "set spec[last() + 1]/user ${name}", "set spec[last()]/host_group/host ALL", "set spec[last()]/host_group/command NOPASSWD: ALL", "set

I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems: *** LOCAL GEMS *** diff-lcs (1.1.3) hiera (0.3.0) hiera-puppet (0.3.0) metaclass (0.0.1) mocha (0.12.1) puppet-lint (0.1.13) puppetlabs_spec_helper (0.2.0) rake (0.9.2.2) rspec (2.11.0) rspec-core (2.11.1) rspec-expectations (2.11.2) rspec-mocks (2.11.1) rspec-puppet (0.1.3) When I run "rake help" I get the

I''ve configured puppet to use storedconfigs and puppetDB, If I start the puppet master using the init script puppetmaster I get a permission denied error when a node connects: Master: [root@puppet ~]# service puppetmaster start Starting puppetmaster: [ OK ] Node: [root@puppet-slave ~]# puppet agent --test err: Could not retrieve catalog from remote

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

cmake -G Ninja -DLLVM_ENABLE_PROJECTS="debuginfo-tests" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DLLVM_TARGETS_TO_BUILD=X86 -Wno-dev ../llvm &> ../../cmake.log in cmake.log -- Targeting X86 CMake Error at /home/nnelson/Documents/llvm-project/debuginfo-tests/CMakeLists.txt:30 (message):   Cannot run debuginfo-tests without python 3 installed python3

We recently fixed the hardwaremodel and architecture facts on Windows as they were always returning i386[1]. The change will be in the upcoming 1.6.10 release of Facter[2]. The new behavior is that hardwaremodel will return something like i686, ia64, x64, etc, while the architecture fact will return either x86 or x64. Since the new behavior will likely affect puppet users that are trying to write

I forgot to mention this in my announcement yesterday. Puppet facts are no longer downcased in the language, and string comparisons now default to being case-insensitive. Where your operating system might previously have been ''solaris'' or ''debian'', it is now ''Solaris'' or ''Debian''. However, you can still do comparisons