Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #186958
| Path | csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.in-chemnitz.de!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Reco <recoverym4n@gmail.com> |
| Newsgroups | linux.debian.user |
| Subject | Re: sudo slow on DNS lookup, with invalid resolv.conf entries |
| Date | Mon, 18 Sep 2017 18:40:02 +0200 |
| Message-ID | <ur7fs-fa-23@gated-at.bofh.it> (permalink) |
| References | <uq1lM-5ih-9@gated-at.bofh.it> <uqQxX-5Q8-3@gated-at.bofh.it> <uqQHD-5Tq-3@gated-at.bofh.it> <uqQRk-6bH-15@gated-at.bofh.it> <uqYc9-2wo-1@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-user-request@lists.debian.org Mon Sep 18 16:39:31 2017 |
| Old-Return-Path | <recoverym4n@gmail.com> |
| X-Amavis-Spam-Status | No, score=-7.799 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: -7 |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Xe6hLMvNOtzsnmhYe+80IlCBlnJinJRlwCNB4omeEmI=; b=r/PiwVkN+lf8CdsRr0NcZ0b1g45Ai2+NG0Xa4RwpzychfXpf01YFu085vco5MXXPe6 3RvuvOejCkgFEqcstxhdfuLncBKD90Brwtt7Xde/wKIDMYbIM1WW4McSpafNMcuZVzmV HT5Px7THChE5FdW6serNIbQp9m16rE/mowJSWw4XWfWADNYz9zmAkZcUjMOCjebLCh9M o61/ERa6T0d5UJzHXgiV4aL95ig4he3/5LZfXcoIL1out9l+MPhOkSe1j9GGUVYWCMw1 C0pLsCjug7QKIs0zIeDLrWxlfYz2fxwVIyInYecCrt8lYi+8EHD79KC4o+NghiG4zSns wBPg== |
| X-Google-Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Xe6hLMvNOtzsnmhYe+80IlCBlnJinJRlwCNB4omeEmI=; b=Uudd7h3dkkCZmCU58wQOhx6bBlxBZn55YfdsX56028oua6SGhDL3np7S9b9PhMxpNW zK7nbtUQMLxToPlqZomLtbTaNvrgAyk5ailiUGTYV44Ss8D3fJwfMLlK+8JeeoxCYk8X awr9ucuDCEdMPjyQI/wqMNY6X2eSdg9GBHQ99xyXnfH9ao5MTUf03p1TvpNx8cJfzkJO iTAHAy3s1SGEOsAdZdqGUIHXG1PFhKThuXwU189t+CFoL87DU6r2W1s4oxIK9EWDbWc6 ZxKfhNsDP3yk8ALknwMXpWyBh5awQRoMoBEDhWUTiPlCD8gZ+LDHNosLWK4Wjf5kJFGU jI9Q== |
| X-Gm-Message-State | AHPjjUgngmc+MCXz0T987FxVlUxh0YWenwL7hTuPyPcYVRL3++VbJY15 S1gNcU11sSNm9RM5 |
| X-Google-SMTP-Source | AOwi7QDiTMubCeWlvXly1iIvtwqCBawqrA+XRhvfSYSOja6Lxs+0jlqteNSTwSH1/BfwbFsodvRIFw== |
| X-Received | by 10.25.154.18 with SMTP id c18mr3864002lfe.165.1505752755561; Mon, 18 Sep 2017 09:39:15 -0700 (PDT) |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=us-ascii |
| Content-Disposition | inline |
| User-Agent | NeoMutt/20170113 (1.7.2) |
| X-Mailing-List | <debian-user@lists.debian.org> archive/latest/726664 |
| List-ID | <debian-user.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-user/> |
| List-Archive | https://lists.debian.org/msgid-search/20170918163911.q63ufo5xoh2slqaq@p5k.home |
| Approved | robomod@news.nic.it |
| Lines | 37 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Mon, 18 Sep 2017 19:39:12 +0300 |
| X-Original-Message-ID | <20170918163911.q63ufo5xoh2slqaq@p5k.home> |
| X-Original-References | <c305125a7fc0d1adf79aa6f6779bb510.squirrel@127.0.0.1> <201709171848.15484.gheskett@shentel.net> <opmume$np7$1@blaine.gmane.org> <201709171909.06045.gheskett@shentel.net> <opnqbj$4kq$1@blaine.gmane.org> |
| Xref | csiph.com linux.debian.user:186958 |
Show key headers only | View raw
Hi. On Mon, Sep 18, 2017 at 08:50:36AM +0200, deloptes wrote: > Gene Heskett wrote: > > > 127.0.0.1 localhost.localdomain localhost > > Sorry but I did not understand if the problem is there or if the problem is > that it is not there? Long story short, OP has a misbehaving Debian stretch installation with the hostname (as in - /proc/sys/kernel/hostname) set to 'localhost.localdomain'. /etc/hosts lacks such entry. /etc/resolv.conf points to an absent DNS. The result is - every execution of sudo has an added 30-second execution time 'bonus'. > I guess this is put there at time of installation. I'll check few virtual > machines later to see how it was written. If the user chooses conventional hostname (even 'debian') during the installation - sure, they should put a record in /etc/hosts. Unsure about stretch, but they did so since etch. The question is - since 'localhost.localdomain' is special, what happens if such hostname is chosen during the installation? > IMO if you have working resolver it shouldn't matter much. Please read this thread's subject one more time. Last three words especially. Reco
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-15 18:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Reco <recoverym4n@gmail.com> - 2017-09-15 19:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-15 21:30 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Reco <recoverym4n@gmail.com> - 2017-09-15 22:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-15 23:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Reco <recoverym4n@gmail.com> - 2017-09-15 23:20 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-15 23:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Reco <recoverym4n@gmail.com> - 2017-09-16 00:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-16 01:20 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Gene Heskett <gheskett@shentel.net> - 2017-09-16 02:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-17 22:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-17 23:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 00:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Gene Heskett <gheskett@shentel.net> - 2017-09-18 00:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-18 01:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Gene Heskett <gheskett@shentel.net> - 2017-09-18 01:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-18 09:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Reco <recoverym4n@gmail.com> - 2017-09-18 18:40 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-18 20:20 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 20:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Reco <recoverym4n@gmail.com> - 2017-09-18 22:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-19 00:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-18 22:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-19 00:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries deloptes <deloptes@gmail.com> - 2017-09-18 23:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-19 00:00 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Gene Heskett <gheskett@shentel.net> - 2017-09-19 00:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Gene Heskett <gheskett@shentel.net> - 2017-09-18 00:50 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Brian <ad44@cityscape.co.uk> - 2017-09-18 01:20 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries Dan Ritter <dsr@randomstring.org> - 2017-09-15 23:10 +0200
Re: sudo slow on DNS lookup, with invalid resolv.conf entries "x9p" <debian-user@x9pneu.com> - 2017-09-15 23:40 +0200
csiph-web