Re: [xcat-user] How can I prevent overwritting of resolv.conf and named.conf?

2014-03-07 Thread Dennis Zheleznyak
You can add the chattr command as a postscript do new nodes will get it or use the following command to set it across the entire cluster: psh chattr +i /etc/resolv.conf On Friday, March 7, 2014, Josh Nielsen wrote: > Thank you Dennis and Jonathan. Setting PEERDNS=no was part of my "fix" to > th

Re: [xcat-user] How can I prevent overwritting of resolv.conf and named.conf?

2014-03-07 Thread Josh Nielsen
Thank you Dennis and Jonathan. Setting PEERDNS=no was part of my "fix" to the ifcfg-eth* files, and I guess that's the best way to prevent revolv.conf from being overwritten then. I also saw the suggestion for chatt +i but would only like to use it as a last resort, since I might loose track of whi

Re: [xcat-user] How can I prevent overwritting of resolv.conf and named.conf?

2014-03-07 Thread Jonathan Mills
What Dennis says should work. However, I think the accepted "Redhat" way of doing it is to put PEERDNS="no" in you /etc/sysconfig/network-scripts/ifcfg-ethX script. On 03/07/2014 12:48 PM, Dennis Zheleznyak wrote: > You can lock the file by entering the following command chattr +i > /etc/resol

Re: [xcat-user] How can I prevent overwritting of resolv.conf and named.conf?

2014-03-07 Thread Dennis Zheleznyak
You can lock the file by entering the following command chattr +i /etc/resolv.conf. This will lock the file even for root. Dennis. On Friday, March 7, 2014, Josh Nielsen wrote: > I have noticed that with my recent restructuring of my cluster's DNS > hierarchy by creating two Service Nodes to st

[xcat-user] How can I prevent overwritting of resolv.conf and named.conf?

2014-03-07 Thread Josh Nielsen
I have noticed that with my recent restructuring of my cluster's DNS hierarchy by creating two Service Nodes to stand in between the compute nodes and the Management Node that I am having two separate problems with files being overwritten once I modify them. Firstly, I configured the SNs to act as