Thanks to Nikola Milutinovic, Paul Roetman and Larry Clegg, who gave
useful hints.
Another thread, "Locking up on CDE login", started by Kevin Dea and
followed by Bob Morningstar, reported the same behavior during consolle
login: the job is endless delayed while starting the CDE interface.
In my case, such delay is correlated with the nameserver defined in
the Bind database not being reachable. I cannot figure why.
My problem 1): slow boot and consolle login when the network is
unavailable. The suggestions were to avoid the conflict between the CDE
interface and network access. Choices include starting the system in
single user mode, setting the network interface down, starting the
consolle in text mode.
No solution seems fully satisfactory to me: I want the system to
start with full functionality if everything is OK, or, in case the
network is not working properly, miss only the services that require
network access.
Problem 2): Have the DNS server working without defining another
nameserver. This box is directly on the Internet, and the desired DNS
behavior is answering all queries taking the information from three
suorces:
1) Internal database for the zones for which it is a primary or
secondary server
2) Cached information from previous queries
3) Access to the root servers for dot (.) domain and down to the servers
for the queried domain.
This is impossible, as far as I understand. The system requires at
least one nameserver address to forward locally unresolved queries.
The original question follows:
Hi,
I am new to Tru64 management. I am running a DS10 with Tru64 4.0F
I have two problems I hope I can receive some hints about. Both are
related to performance when the network (Ethernet LAN connected to IP
via router) is missing or broken.
I wish my machine can be booted and used locally even when the
Ethernet cable is disconnected. How can I obtain that?
1) If the Ethernet cable is disconnected, booting the machine produces
extremely long delays. Similar problems are encountered if the cable is
connected, but the configured nameserver is not reachable.
Once the system is up, long delays are still met during a consolle
login, while starting the graphical interface. In this case, if the
network is connected, network accesses (telnet) can be done at full
speed.
2) Bind configuration. I configured the machine as a DNS server. The
configuration interface requires defining one or more external
nameservers. On the contrary, I wish the server not to depend on any
defined nameserver, except the root nameservers defined in named.ca
At present, the system is configured not to act as a primery or
secondary nameserver for any zone.
Can anybody give hints on these problems? Are my expectations
reasonable? If so, how can I get them working?
Gustavo Avitabile
Received on Fri Jul 07 2000 - 10:46:31 NZST