On Thu, April 11, 2019 20:17, Solene Rapenne wrote: > Hi > > I just wanted to report that misc/mc (midnight commander) won't start if > your network is set, a gateway is set but doesn't have network access > because it wants to resolve the system hostname. If no network is > available, it doesn't try and starts correctly.
Hi! I've seen this on OpenBSD and Linux and adding hostname 127.0.0.1 to /etc/hosts was solving the problem. It will start anyway but it will take a lot of time if it could not resolve hostname. > > tcpdump output when starting mc with network, I modified the dns server to > 1.1.1.1 to make it more readable. My system hostname is solene.perso.local > > 19:13:34.222774 192.168.43.56.4541 > 1.1.1.1.53: 26065+ A? > solene.perso.local.(36) > 19:13:34.797038 1.1.1.1.53 > 192.168.43.56.4541: 26065 NXDomain 0/1/0(111) > [tos 0x50] > 19:13:34.797261 192.168.43.56.30463 > 1.1.1.1.53: 11960+ A? > solene.perso.local.perso.local.(48) > 19:13:34.872702 1.1.1.1.53 > 192.168.43.56.30463: 11960 NXDomain 0/1/0(123) > [tos 0x50] > 19:13:34.872931 192.168.43.56.27907 > 1.1.1.1.53: 30605+ A? > solene.perso.local.(36) > 19:13:34.941878 1.1.1.1.53 > 192.168.43.56.27907: 30605 NXDomain 0/1/0(111) > [tos 0x50] > 19:13:34.943321 192.168.43.56.8533 > 1.1.1.1.53: 15521+ A? > solene.perso.local.(36) > 19:13:35.019228 1.1.1.1.53 > 192.168.43.56.8533: 15521 NXDomain 0/1/0(111) > [tos 0x50] > 19:13:35.019476 192.168.43.56.42298 > 1.1.1.1.53: 46078+ A? > solene.perso.local.perso.local.(48) > 19:13:35.164569 1.1.1.1.53 > 192.168.43.56.42298: 46078 NXDomain 0/1/0(123) > [tos 0x50] > 19:13:35.164788 192.168.43.56.41654 > 1.1.1.1.53: 42999+ A? > solene.perso.local.(36) > 19:13:35.289600 1.1.1.1.53 > 192.168.43.56.41654: 42999 NXDomain 0/1/0(111) > [tos 0x50] > > I have no idea why mc requires this. It looks like more a bug than a feature > to > me. It leaks your hostname to your resolver which is a bit weird. > >
