Subject: | |
From: | |
Reply To: | |
Date: | Fri, 8 Apr 2011 13:00:32 +1000 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Wed, 2011-04-06 at 22:24 -0700, Steven J. Yellin wrote:
> I don't know if doing something in a %pre script is appropriate for
> your situation, but even if it is, "chmod a-w /etc/resolv.conf" might not
> prevent NetworkManager from changing the file. I believe NetworkManager
> runs as root, and if as root you try such a chmod command on a file,
> you'll find that root has no problem changing the file. But root doing
> "chattr +i /etc/resolv.conf" should protect resolv.conf. After that
> chattr command even root can't change resolv.conf without first doing
> "chattr -i /etc/resolv.conf".
>
> Steven Yellin
>
> On Thu, 7 Apr 2011, Ahmed El Zein wrote:
>
> > Nico,
> > Thanks for that. I don't have NetworkManger installed in by base system.
> > My problem is how do I stop NetworkManger running during the anaconda
> > install process while kickstarting? From what I can gather everything
> > works fine until it starts. one it starts it ruins the /etc/resolv.conf
> > file and all my %post scripts fail.
> >
> > can I do something in a %pre script that will prevent NetworkManger from
> > editing anything. maybe a "chmod a-w /etc/resolv.conf"?
> >
> > Thanks,
> > Ahmed
It looks like this is a RHEL6 bug.
https://bugzilla.redhat.com/show_bug.cgi?id=637193
Thanks,
Ahmed
|
|
|