Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #186930
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: sudo slow on DNS lookup, with invalid resolv.conf entries |
| Date | 2017-09-18 09:10 +0200 |
| Message-ID | <uqYlP-2Ut-11@gated-at.bofh.it> (permalink) |
| References | <uqRu1-6qe-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
x9p wrote: > 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. This is the default from the last stretch install $ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 fujitsu.mydomain fujitsu so if mydomain or localdomain is not working it will delay. 127.0.1.1 fujitsu fujitsu.mydomain will not delay because fujitsu is the name of the machine. in my case mydomain was added at installation time, because cable was plugged in and the computer (fujitsu) got its IP via the dhcp server on the local network. IMO you should look deeper in your use case and see why you get invalid setup. The problem might be somewhere else. regards
Back to linux.debian.user | Previous | Next — Previous in thread | 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