as well as showing you all of the
> intermediate requests.
Which is probably why the masses like nslookup. 99 times out of 10,
they just want to know the IP for a given name and aren't especially
interested in much of anything else.
rick jones
--
firebug n, the idiot who tosses a lit ci
Marc Brett <[EMAIL PROTECTED]> wrote:
> Second, the December 6 event dramatically shows the effect of solar
> radio bursts is global and instantaneous.
Instantaneous? I thought it took at least 8 minutes for something
happening at the Sun to become "visible" near Earth?
r
t depends on whether or not ntpdate wants to see IP addresses
it won't use - ie filter/ignore them itself rather than letting
getaddrinfo do it.
rick jones
--
The glass is neither half-empty nor half-full. The glass has a leak.
The real question is "Can it be patched?"
these opinions
v6 answers when there is no IPv6 address configured on the
system running ntpdate.
Whether ntpdate should be enhanced to walk the list I guess would be
an open question.
rick jones
--
The glass is neither half-empty nor half-full. The glass has a leak.
The real question is "Can it be patched?
ere is an interface
configured with a v6 address. Loopback (IIRC) does not
count. (leaving open I suppose the question of what happens with that
set and only a loopback address configured :)
rick jones
--
Wisdom Teeth are impacted, people are affected by the effects of events.
these opin
, we can ass-u-me :) that most of the delay is actually
somewhere other than the wire in the test above, and then that the
dleay for 100BT would be roughly the same. (of course, as the request
and response sizes increase, link bitrate will become a component of
the delay greater than epsilon)
rick
ing/briefs/nic_latency_vs_tput.txt
has some jumbled results of what can change based on some tests I've
run in the past.
hth,
rick jones
--
oxymoron n, commuter in a gas-guzzling luxury SUV with an American flag
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to po
