search for: traylen

...20.7 append root=/dev/nfs nfsroot=.... ip=dhcp and now everything is working for fine for us. We have a work around but I thought I would report the problem we saw as I'm interested in what is going on. I guess pxelinux.0 interrogating the NIC is going wrong somewhere. Steve -- Steve Traylen s.traylen at rl.ac.uk http://www.gridpp.ac.uk/

I am currently using Puppet''s firewall module: http://forge.puppetlabs.com/puppetlabs/firewall I am trying to have Puppet flush iptables before it applies firewall rules. I tried the following: exec { ''clear-firewall'': command => ''/sbin/iptables -F'', refreshonly => true, } Firewall { subscribe =>

> - your SteveTraylen straylen > - inform them that you are a member of the ConfigManagementSig Hi I am a member of the ConfigManagementSig > - Ask to have access to 1. your personnal page 2. https://wiki.centos > .org/SpecialInterestGroup/ConfigManagementSIG Please may I have access to my personal page th...

How do folks feel about getting Puppet job listings on this list? I''ve rejected a few that we quite spammy, but when the subject matter really is a system admin with puppet experience, the decision becomes a bit different. I''m looking for general feelings. A simple +1 or -1 would be great. Mike -- You received this message because you are subscribed to the Google Groups

Hi, This follows on a bit from the previous thread ''trouble with hiera and puppet defines'' [1] Up to now I''ve had a large file of virtual resources and then enabled them on demand on various services. The very standard. @metric{''1234: one => 1 two => [1,2] } @metric{''abcd'': one => a, two => [b,c] } and

Hi, am trying this rule: firewall { ''100 allow ssh from GUNET'': proto => ''tcp'', dport => ''22'', source => [''10.0.0.0/8'',''192.168.0.0/16'',], action => accept, } and it only seems to add a rule for the first subnet. The second is silently