1 |
> On 10/11/2010 11:38 PM, daid kahl wrote: |
2 |
> |
3 |
>> However, I noticed that logins, su, and sudo are all responding |
4 |
>> slowly. This was all fixed and fine once I updated my configuration |
5 |
>> files, but this week it's acting up again. Before it was just su and |
6 |
>> sudo that I noticed as slow (authentication takes around 20 seconds). |
7 |
>> But now even logins are delayed (xdm or command line). |
8 |
|
9 |
On 13 October 2010 07:12, walt <w41ter@×××××.com> wrote: |
10 |
> |
11 |
> Whenever I see something that eventually works, but only after a long |
12 |
> delay, I think of DNS problems. |
13 |
> |
14 |
> Who might be doing a nonsensical DNS lookup, I have no idea. But you |
15 |
> might consider running a packet sniffer (wireshark, etc) while logging |
16 |
> in or doing an su. Are you running your own local name server? |
17 |
|
18 |
Very very intersting!! |
19 |
|
20 |
The main correlation I've seen so far is with dhcpcd. Sometimes at my |
21 |
work I get a 192. IP (which doesn't work), and other times I get a |
22 |
133. IP (which is correct). In fact, sometimes dhcp is giving me an |
23 |
IP address and resolv.conf related to a university I was visiting like |
24 |
a month ago. |
25 |
|
26 |
In other words, I know I have some networking problems, but I was |
27 |
reluctant to imagine it was at all related to this login problem, even |
28 |
though I had some basic empirical data on it. |
29 |
|
30 |
Anyway, it happened again tonight, and it was resolved after I did |
31 |
some of the same emerges as before, but I think that might be just |
32 |
chance. |
33 |
|
34 |
I look into the DNS stuff. Thanks for the sanity check! |
35 |
|
36 |
~daid |
37 |
|
38 |
PS: Sorry for the initial top posting on myself... |