Ever since I have used RedHat 9/D3 Linxu 7.4.0 (previously used RedHat
5.2/D3 Proplus), I've experienced a delay when starting D3 on a telnet
session. This delay after "/dev/pts/0: Connected to Virtual Machine
'pick0:LINUX'." is between 10-13 seconds. There is no delay in the
initial telnet and logging into Linux. This is lightning fast.

This delay only exists if there is an entry in the hosts file for that
client that is telnetting in. If there is no entry, the delay does not
exist and d3 starts up instantly.

I need the entries in the host file. Does anyone know what is causing
this?

D3 must be doing some sort of resolving on the IP address or name.
It's opposite to what you'd expect.

matt (AT) ox11 (DOT) com wrote:
Hi Matt.

What resolver services have you got running on your Redhat box?

John.

Check to ensure that your Linux machine is pointing to a
valid/functioning DNS server - IIRC a standard Linux install will take
a manually assigned IP address for your machine & work out where it
thinks your DNS server probably is - it has been known to guess wrong !

The server is not pointing to a DNS server. The server is not on the
internet and no other DNS server exists. The clients are using fixed
IP addresses and telnetting to the server IP address and therefore no
name resolving required. I would of expected this delay to exist if
there was nothing in the host file, as there is then nothing to
reference/resolve. However, when an entry exists for that client, the
D3 delay exists.
Also, the other point to remember is that this isn't a Linux delay.
The Linux session is quite happy whether the host file is populated or
not. It is only when D3 is started that the delay exists. D3 must be
doing something with the IP address or host name when it starts up.

Matt,

What is the problem with just putting all your fixed IP addresses in
the host file? It works for me.

Douglas



Matt wrote:

matt (AT) ox11 (DOT) com wrote:


I also had a similar problem, traced it down to iptables. If you are
not connected to the internet try (from root):

service iptables stop

see if this resolves the delay issue.

"Matt" wrote
delay, I think you'll find a host command running; in other words, d3
is asking linux to please do some sort of reverse dns lookup. Once you've
verified that assertion, your problem reduces to making that host command
on the linux side run faster. You really ought to state what linux version you
run on, as people reading this thread in Google a year or three from now
won't have the foggiest idea when this release of d3/linux was current...