Comment 4 for bug 1628552

Revision history for this message
just me (nevdull) wrote :

well i've now been able to restart 3 of the 4 systems about 5-10x each through the day. all have had their gateway and dns- settings from /e/n/i reliably set. that is, until now. i've got one system that did not get gateway or dns- settings.

is there a way to check for a failure status code tied to ifup or resolvconf runs during startup?

$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
  address x.y.105.96
  netmask 255.255.252.0
# network x.y.104.0
  broadcast x.y.107.255
  gateway x.y.107.250
# dns-* options are implemented by the resolvconf package, if installed
  dns-nameserver x.y.105.44
  dns-nameserver x.y.147.98
  dns-search r.mydomain s.mydomain t.mydomain

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

note: i have since removed the comments from base & tail.