Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #186927
| From | "x9p" <debian-user@x9pneu.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: sudo slow on DNS lookup, with invalid resolv.conf entries |
| Date | 2017-09-18 01:50 +0200 |
| Message-ID | <uqRu1-6qe-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
> The last time I recollect this "someone" sticking his head above the parapet was in the thread beginning at > https://lists.debian.org/debian-devel/2013/07/msg00809.html >From the above URL: From: Christoph Anton Mitterer <calestyo@scientia.net> Date: Tue, 30 Jul 2013 22:43:44 +0200 ----- - The system hostname (and domainname if any) should ALWAYS be resolvable, whether a network is up or not, regardless of which. (Assuming that lo is always up, if not, many things break anyway.) - "localhost" when added like this to /etc/hosts is basically like a TLD. "localhost" is one of the reserved names, unlike ip6-localhost and friends and unlike .localdomain. ... ... ... Further, but this isn't the case anymore anyway,... we should not generate localhost.localdomain. ... ... ... ----- If system hostname should ALWAYS be resolvable, whether there is network or no, the change in /etc/hosts from (default in stretch): 127.0.0.1 localhost to (my system): 127.0.0.1 localhost localhost.localdomain is justifiable as it breaks (not literally break, just adds lot of delay) to sudo in a non-networked environment. x9p
Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 01:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-18 09:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 11:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Curt <curty@free.fr> - 2017-09-18 13:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-18 16:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Curt <curty@free.fr> - 2017-09-18 16:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 17:30 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 18:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 20:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 21:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 14:40 +0200
csiph-web