| 1 |
Hi Jason, |
| 2 |
|
| 3 |
Try using an empty file for /etc/resolv.conf |
| 4 |
|
| 5 |
When no file is found your computer will try to lookup the name of your host using the resolv protocol. When a resolv.conf file is found, the resolver will use all methods specified. An empty file specifies no method to resolve so none are used. |
| 6 |
|
| 7 |
Hope this helps you. |
| 8 |
|
| 9 |
Regards, |
| 10 |
Cees |
| 11 |
|
| 12 |
|
| 13 |
----- Original Message ----- |
| 14 |
From: "Jason" <gentoo@××××××××××.net> |
| 15 |
To: gentoo-embedded@l.g.o |
| 16 |
Sent: Wednesday, February 20, 2008 4:15:17 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna |
| 17 |
Subject: [gentoo-embedded] dropbear, gethostbyname(), timeout |
| 18 |
|
| 19 |
Ok, stupid question time. :-) |
| 20 |
|
| 21 |
I'm trying to do the correct, longterm solution for the following |
| 22 |
problem. When I ssh into my board (running dropbear-0.49), if I don't |
| 23 |
have the client's ip address and hostname in /etc/hosts (on the board), |
| 24 |
it'll take over a minute to log in. Presumably hung on gethostbyname() |
| 25 |
or similar. |
| 26 |
|
| 27 |
Adding the name and ip to /etc/hosts is fine while I'm putzing around, |
| 28 |
but once I deploy it, I can't guarantee what network (crossover cable?) |
| 29 |
it'll be on, or what the client ip or hostname will be. I'm using |
| 30 |
udhcpc to bring the device up and I've used |
| 31 |
/usr/share/udhcpc/default.script to dynamically write the |
| 32 |
/etc/resolv.conf file based on input from the network's dhcp server. |
| 33 |
But nothing I've tried works. |
| 34 |
|
| 35 |
Has anyone encountered this? What's the proper fix? |
| 36 |
|
| 37 |
thx, |
| 38 |
|
| 39 |
Jason. |
| 40 |
-- |
| 41 |
gentoo-embedded@l.g.o mailing list |
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-embedded@l.g.o mailing list |
Archives