[Spacewalk-list] Prevent client changes to Centrally Managed Configuration files

[Justin Edmands]

I would like to prevent client changes from being made to centrally managed
configuration files. Or, maybe just overwrite the changes with the central
file in order to prevent slip ups. Anyways, aside from permissions and
selinux, how can I prevent changes to the clients instance of the centrally
managed configuration file? I feel like I had it working in the past. It
seemed like a simple rhn_check seemed to overwrite any changed files.

This is mostly so I can lock down files from the users that like to "test"
things and don't think to changes the files back.

I found a similar post from 3 years ago. I was hoping this sort of thing
exists by now:
http://www.redhat.com/archives/spacewalk-list/2010-February/msg00050.html



Misc gripes that may be fixed that I am unaware of:
 - I still do not like the fact that you cannot create a "Locally Managed"
configuration file channel to upload files to using the rhncfg-manager.
 - Any way to get the OSAD status on the Systems main page? Maybe a column
next to Health or Entitlement that shows the time and make it clickable to
send a ping. Ahh I'm just dreaming, right?


--

Justin Edmands
shockwavecs at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130503/81fb073c/attachment.htm>