etc/resolv.conf gets overwritten with blank file upon boot.

[Paul Howarth]

On Tue, 2005-03-08 at 16:38 -0500, Nat Gross wrote:
> Paul Howarth wrote:
> 
> >On Tue, 2005-03-08 at 14:01 -0500, Nat Gross wrote:
> >  
> >
> >>>Go to /etc/sysconfig/network-scripts and edit the script which sets on
> >>>your interface. There shouldn't be any line with DHCP, just comment
> >>>them or remove them.
> >>> 
> >>>
> >>>      
> >>>
> >>Hmm... I am not that well versed with scripting bash. Also, are these 
> >>scripts automatically generated? Should I not rather goto the source 
> >>that causes the script be written? What happens if I turn dhcp on again 
> >>in the future?
> >>    
> >>
> >
> >Try this:
> >$ fgrep BOOTPROTO /etc/sysconfig/network-scripts/ifcfg-*
> >
> >If any of the resulting output (which might be empty) mentions DHCP then
> >edit the referenced file and change
> >
> >BOOTPROTO=dhcp
> >
> >to
> >
> >BOOTPROTO=static
> >
> >Paul.
> >  
> >
> On both machines, BOOTPROTO is already set to static. (It happens on 
> both FC3 machines.)

Have you ever tried running NetworkManager on either of these machines?
That might do this.

Could you look at the exact timestamp of the empty resolv.conf file and
compare it with the entries in /var/log/messages
and/or /var/log/boot.log to figure out where in the boot process this
happens?

If you do "service network restart" does this happen?

Paul.
-- 
Paul Howarth <paul at city-fan.org>