From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from <gentoo-user+bounces-115665-garchives=archives.gentoo.org@lists.gentoo.org>) id 1P6Bgl-0008PL-9G for garchives@archives.gentoo.org; Thu, 14 Oct 2010 00:28:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 56744E07A5; Thu, 14 Oct 2010 00:28:01 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 1E78EE0917 for <gentoo-user@lists.gentoo.org>; Thu, 14 Oct 2010 00:28:01 +0000 (UTC) Received: by wyf22 with SMTP id 22so7354681wyf.40 for <gentoo-user@lists.gentoo.org>; Wed, 13 Oct 2010 17:28:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=epwq+dK38YV6XN/Bv5qKxIM8Dc3FcUN8U2t86c1NVes=; b=sagIRv5/o4kTTwDXLrlji3kIA3SPND9mkQ7+kc5CsEpDEDxbLJTxMFLjOBJNXVlWsb YmUQq9EbKhu2GTlnAeX/nzgJChazo9sjw4yKXi3StyHYy48Pbjojqvs9LQd94/n+YZeA FzEpcfi0KWPbGsd3eu5oBVl05+Jvk9EE6Mszg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=kLnB/m51kLiO8OSwIdkhra7OvVy5yZoFMQx75y+Ft7jztaIbmGc8AwkOCL2XGC2qU8 ZhZ9qVJ4lyszM37wAMjKz0rUFvmJEPPnn3Xe9WA2NWfYCdTonEZJqYVX1uaWC3JitGEz W2FG8QV/DL1PJ6juZ4ERJPeAQBzdg94YXlOgc= Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.164.199 with SMTP id c49mr9053695wel.107.1287016080529; Wed, 13 Oct 2010 17:28:00 -0700 (PDT) Received: by 10.216.175.13 with HTTP; Wed, 13 Oct 2010 17:28:00 -0700 (PDT) In-Reply-To: <AANLkTikXST0EiHD0NbHU6HSqAXFUeYKBVc9LLjWhs4U3@mail.gmail.com> References: <AANLkTimX3aBuUeZJxOb_+Tcwj-wajOe2wtC6Jsj07nL0@mail.gmail.com> <i92mge$6us$1@dough.gmane.org> <AANLkTikXST0EiHD0NbHU6HSqAXFUeYKBVc9LLjWhs4U3@mail.gmail.com> Date: Wed, 13 Oct 2010 17:28:00 -0700 Message-ID: <AANLkTi=ddp84gR-a-xBpLhJzqwOhbd-0CPsSAS2VeWhe@mail.gmail.com> Subject: Re: [gentoo-user] Re: Slow Login, Sudo, etc. From: James Ausmus <james.ausmus@gmail.com> To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: a224837f-cc70-401a-9161-55e1feba4861 X-Archives-Hash: a00f61e792376d650ed63fa2fd233d0b On Wed, Oct 13, 2010 at 6:38 AM, daid kahl <daidxor@gmail.com> wrote: >> On 10/11/2010 11:38 PM, daid kahl wrote: >> >>> However, I noticed that logins, su, and sudo are all responding >>> slowly. =A0This was all fixed and fine once I updated my configuration >>> files, but this week it's acting up again. =A0Before it was just su and >>> sudo that I noticed as slow (authentication takes around 20 seconds). >>> But now even logins are delayed (xdm or command line). > > On 13 October 2010 07:12, walt <w41ter@gmail.com> wrote: >> >> Whenever I see something that eventually works, but only after a long >> delay, I think of DNS problems. >> >> Who might be doing a nonsensical DNS lookup, I have no idea. =A0But you >> might consider running a packet sniffer (wireshark, etc) while logging >> in or doing an su. =A0Are you running your own local name server? > > Very very intersting!! > > The main correlation I've seen so far is with dhcpcd. =A0Sometimes at my > work I get a 192. IP (which doesn't work), and other times I get a > 133. IP (which is correct). =A0In fact, sometimes dhcp is giving me an > IP address and resolv.conf related to a university I was visiting like > a month ago. It sounds like someone at your work might be (accidentally) running a rogue DHCP server... -James