Solaris

Run this from your home directory after you log in:

Code:

touch .hushlogin

Try logging in again.

The default login process is to run a quota check for space usage against all files systems. If the server you're logging into has a lot of file systems - especially NFS-mounted file systems - that can take a while.

Usually creating a ".hushlogin" file in your home directory will disable the quota checks.

If that doesn't work, you really need root access to definitively locate the issue.

Find the "parent" sshd daemon, then as root run truss against it:

Code:

 truss -f -a -vall -l -d -o /some/SECURE/output/file -p SSHD_PID

Make SURE the output file you select is secure - it will have your password embedded in it if you use password authentication. And that of everyone else who logs in while the truss process is running.

While that's running, log in, log out, kill the truss process, and look into the output. You'll see all the system calls made by the original sshd daemon, along with all the child processes fork()'d off. Somewhere in there, you'll see some long delays. Whatever is taking long to do, that's where your delay is.

bash-3.00$ less /etc/defaultrouter 192.168.2.333


There's yer problem.

i had the similar issue on one of my server. Was related to a DNS misconfiguration.
take very long to connect (estabilish a connection to the host) and also to login!

my suggestion is to recheck your dns configuration.

is there a sapce or tab (are not allowed) after "domain macau.com" in your resolv.conf file?

or what you can try is to save the hostname and ip of your remote server in your /etc/hosts file. If it's faster than you have a problem in you dns config!!

Hi sbk1972, tommyk, echenle, beta17,

I combined all your approach it works well, I’m really impressed. Salute you guys. Many thanks.

Regards,
FSP

and what exactly solved your issue? :-)