From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 66A2113877A for ; Sun, 27 Jul 2014 19:13:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 01DC4E0C1D; Sun, 27 Jul 2014 19:13:28 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id E1BFCE0BFF for ; Sun, 27 Jul 2014 19:13:26 +0000 (UTC) Received: from digimed.co.uk (shooty.digimed.co.uk [192.168.1.8]) by mail.digimed.co.uk (Postfix) with ESMTPA id BBEB422ABB for ; Sun, 27 Jul 2014 20:13:25 +0100 (BST) Date: Sun, 27 Jul 2014 20:13:22 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] resolv.conf is different after every reboot Message-ID: <20140727201322.3397d2f4@digimed.co.uk> In-Reply-To: References: <20140727102923.7229724e@hactar.digimed.co.uk> Organization: Digital Media Production X-Mailer: Claws Mail 3.10.1-119-g7fbc83 (GTK+ 2.24.24; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/F1sX00i.CugVQE93NVP0AQ4"; protocol="application/pgp-signature" X-Archives-Salt: 3be1d5b7-a1c8-4e1c-8dcb-4a9db3936ce8 X-Archives-Hash: 14a6e7bdd7f2755f288c4cd2ebf693cc --Sig_/F1sX00i.CugVQE93NVP0AQ4 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote: > > That's what replaces it when eth0 comes up. > > It looks like eth0 is not being brought up fully =20 >=20 > It sounds logical. But how can I fix it? By identifying how far it is getting and why no further. But it appears that eth0 is being brought up correctly and then the config is overwritten by the lo config. I'd suggest going with the suggestion of disabling hotplugging for net.* interfaces. =20 > > what do your logs say? =20 >=20 > Could you, please, be more precise where to look for "logs". /var/log/messages, dmesg, the standard places. > > It might be worth putting logger commands in preup(), > > postup() and failup() in conf.d/net. =20 >=20 > Currently, I have no such functions in my /etc/conf.d/net file. > Shall I copy them there from > /usr/share/doc/netifrc-0.2.2/net.example Yes, they are run are various stages of bringing up the interface. > Could you, please, be more specific on these "logger commands" too. I meant to add a logger call to each function to see how far it gets logger "eth0 going up" logger "eth0 up" logger "eth0 failed" or something like that. but it appears this is moot and eth0 is up successfully.=20 > > BTW, I'm not sure if it's still relevant, but I don't think you ever > > posted the contents of /etc/resolvconf.conf, if it exists. =20 >=20 > I do not have such file. Of course, if you do not mean /etc/resolv.conf > But I have posted its content above. I meant /etc/resolvconf.conf, which you were asked for before, but as you don't have it, the problem isn't there.=20 --=20 Neil Bothwick Vital papers will demonstrate their vitality by moving to where you can't find them. --Sig_/F1sX00i.CugVQE93NVP0AQ4 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPVT1IACgkQum4al0N1GQO3+wCgi68jt6LHWfCsuHLhpIaHDWhO PAYAn06AVpEuuwA6rDMd/If+k0uHifWG =F1ND -----END PGP SIGNATURE----- --Sig_/F1sX00i.CugVQE93NVP0AQ4--