Andreas ..
Andreas Höschler wrote:
Is such an entry in /etc/hosts really necessary? My /etc/nsswitch.conf has "dns files" for resolving host names. I configured SGD for one fully qualified domainname that can be resolved via dns to the ipaddress of the machine. SGD basically works for me. However, it is extremely slow. It takes 30-40s (telnet) to fireup a Window Maker FullScreen session and that on a 2 x 1.6GHz machine with nothing else to do and even much more when using ssh for the connection method. The old SunFire 280 2 x 900MHz presented a better performance. I am wondering whether this is due to a suboptimal configuration of SGD (timeouts,...). Any idea how I could further track this down?
Possibly caused by SGD timeouts. More info here:
http://docs.sun.com/source/820-2550/launch_timeouts.html

Some other thoughts .. are your SGD application servers configured by IP or hostname? I'm wondering if they're hostname, and the dns lookups are taking a long time.

Outside of an SGD session, test from a command line on the SGD box
- nslookup <sgd-peer-hostname> [this is typically the name you set at install time]
- nslookup <application-server>
- test making a connection to the app server (e.g. ssh/telnet, etc).

If the above results show slow DNS (I've seen this, and also intermittent/flakey DNS responses) then try putting the DNS names into the SGD server /etc/hosts and modifying nsswitch.conf so it reads "files dns" i.e. reverse the order... then run the above tests.

Note the SGD install guides says DNS is a requirement and we always push for this, but this alternative approach falls under the "unless you know what you're doing" umbrella :)

Curtis.


--


Desktop Technical Specialist
Sun Microsystems
accessline: (310) 464-6289
internal: 41621


_______________________________________________
SGD-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sgd-users

Reply via email to