| 1 |
On 26/06/2014 12:45, Stefan G. Weichinger wrote: |
| 2 |
> Am 26.06.2014 06:07, schrieb Dale: |
| 3 |
> |
| 4 |
>> I ran into a issue like this once a long time ago. I had something |
| 5 |
>> wrong with my hosts file if I recall correctly. It never did make sense |
| 6 |
>> as to how it messed things up but after fixing that, it worked fine. |
| 7 |
>> So, I'd look at the hosts file and see if anything is amiss there. I'm |
| 8 |
>> pretty sure that is the file that was messed up tho. |
| 9 |
>> |
| 10 |
>> Hope that helps. |
| 11 |
> |
| 12 |
> thanks for the suggestion. |
| 13 |
> I don't see anything strange in the hosts file(s). |
| 14 |
> |
| 15 |
> For now I keep pam_systemd commented out. Maybe I upgrade to systemd 214 |
| 16 |
> on that server ... ssh-ing to my main workstation works fine with that |
| 17 |
> line in /etc/pam.d/system-auth ... so maybe it's related to the release |
| 18 |
> of systemd. |
| 19 |
> |
| 20 |
> Stefan |
| 21 |
> |
| 22 |
> |
| 23 |
> |
| 24 |
> |
| 25 |
|
| 26 |
|
| 27 |
Is your delay about 30 seconds? |
| 28 |
If so, that's almost certain to be related to dns lookups (30 seconds |
| 29 |
being the magic timeout that almost everything seems to use) |
| 30 |
|
| 31 |
-- |
| 32 |
Alan McKinnon |
| 33 |
alan.mckinnon@×××××.com |
Archives