From: James Ausmus <james.ausmus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Slow Login, Sudo, etc.
Date: Wed, 13 Oct 2010 17:28:00 -0700 [thread overview]
Message-ID: <AANLkTi=ddp84gR-a-xBpLhJzqwOhbd-0CPsSAS2VeWhe@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikXST0EiHD0NbHU6HSqAXFUeYKBVc9LLjWhs4U3@mail.gmail.com>
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. This was all fixed and fine once I updated my configuration
>>> files, but this week it's acting up again. Before 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. But you
>> might consider running a packet sniffer (wireshark, etc) while logging
>> in or doing an su. Are you running your own local name server?
>
> Very very intersting!!
>
> The main correlation I've seen so far is with dhcpcd. Sometimes at my
> work I get a 192. IP (which doesn't work), and other times I get a
> 133. IP (which is correct). In 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
next prev parent reply other threads:[~2010-10-14 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 6:38 [gentoo-user] Slow Login, Sudo, etc daid kahl
2010-10-12 7:12 ` [gentoo-user] " daid kahl
2010-10-12 7:13 ` daid kahl
2010-10-12 14:42 ` [gentoo-user] " Paul Hartman
2010-10-12 22:12 ` [gentoo-user] " walt
2010-10-13 13:38 ` daid kahl
2010-10-14 0:28 ` James Ausmus [this message]
2010-10-14 0:57 ` Adam Carter
2010-10-15 7:24 ` daid kahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=ddp84gR-a-xBpLhJzqwOhbd-0CPsSAS2VeWhe@mail.gmail.com' \
--to=james.ausmus@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox