= problem = A grep through the existing puppet tree showed nothing for /etc/resolv.conf management. I have added this with a simple template, I decided against using a template because it would only be expensive in compiling the manifest. If there is something I don't know and we require different nameservers or similar, I'm more than happy to make it a template and pull some data from facter.
= analysis = A lack of control over /etc/resolv.conf
= enhancement recommendation = Implement the patch, the patch can then be used with: include network::resolv
Patch for the existing puppet tree scrothers.patch
we manage resolv.conf in global, now
file { "/etc/resolv.conf": source => [ "puppet:///config/system/resolv.conf/resolv.conf.$hostname", "puppet:///config/system/resolv.conf/resolv.conf.$pup_datacenter", "puppet:///config/system/resolv.conf/resolv.conf.$datacenter" ], }
not sure I understand the screen patch - what is it fixing?
The screen change is to simply fix a common issue where the permissions are incorrect and prevent screens from being made for non-root users.
I utilize it in my puppet modules simply as a safety net, that way I don't get issues later for whatever reason.
'''Reference:'''[[BR]] https://bugs.launchpad.net/ubuntu/+source/screen/+bug/390405 [[BR]] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471763 [[BR]] http://www.noah.org/wiki/Screen_notes [[BR]] https://bugzilla.redhat.com/show_bug.cgi?id=233527