> this gives, but i am unsure what it means re my problem [ssh takes
> O(20)sec)]:
Hi Michael,
here it is what's taking so long:
> execve("/usr/bin/ssh", ["ssh", "-p", "87",
> "michael@ratty.phy.umist.ac.uk", "w"], [/* 28 vars */]) = 0
> [snipping lots of output]
> open("/etc/resolv.conf", O_RDONLY) = 3 <0.000031>
> fstat64(3, {st_mode=S_IFREG|0644, st_size=54, ...}) = 0 <0.000018>
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0x40018000 <0.000022>
> read(3, "search\nnameserver 192.168.0.1\nna"..., 4096) = 54 <0.000048>
> read(3, "", 4096) = 0 <0.000019>
> close(3) = 0 <0.000018>
Hm, your resolv.conf mentions the host 192.168.0.1 as primary
DNS server... this is giving problems later on... are you sure
that there's a DNS server running (and responding) there?
> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000046>
Creating a UDP socket...
> connect(3, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("192.168.0.1")}, 28) = 0 <0.000030>
Connecting to the primary DNS server...
> send(3, "\274\177\1\0\0\1\0\0\0\0\0\0\5ratty\3phy\5umist\2ac\2"..., 39,
> 0) = 39 <0.000080>
Transmitting query...
> gettimeofday({1109534905, 304051}, NULL) = 0 <0.000016>
> poll([{fd=3, events=POLLIN}], 1, 5000) = 0 <5.001755>
And waiting 5 seconds (!) for an answer...
> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4 <0.000050>
> connect(4, {sa_family=AF_INET, sin_port=htons(53),
> sin_addr=inet_addr("212.1.130.32")}, 28) = 0 <0.000030>
> send(4, "\274\177\1\0\0\1\0\0\0\0\0\0\5ratty\3phy\5umist\2ac\2"..., 39,
> 0) = 39 <0.000074>
> gettimeofday({1109534910, 306824}, NULL) = 0 <0.000016>
> poll([{fd=4, events=POLLIN, revents=POLLERR}], 1, 5000) = 1 <0.043725>
> ioctl(4, FIONREAD, [0]) = 0 <0.000020>
> recvfrom(4, 0xbfffdc60, 1024, 0, 0xbfffd174, 0xbfffd134) = -1
> ECONNREFUSED (Connection refused) <0.000023>
> close(3) = 0 <0.000037>
> close(4) = 0 <0.000027>
... until it connects one of the other servers and gets answer
from it in no time (ok, 43ms, but that's "no time"). ;-)
This repeats three more times, giving you a complete connection time
of about 20 seconds.
I'd suggest checking the DNS server on 192.168.0.1, or at least
temporarily swapping the order in /etc/resolv.conf, so the one
that's most likely to respond is listed first.
Regards,
Jan
--
Jan C. Nordholz
<jckn At gmx net>
Attachment:
signature.asc
Description: Digital signature