My problem seems to have fixed itself...!!! This issue started at 3pm and resolved itself at 9:45am the next day... I believe that Paul and Chris hit the nail on the head with a DNS issue... (maybe some network changes were made.... but we will never know...) see below... Paul.Sagneri@cox.com It's a DNS issue. The DNS servers default to 60 seconds and they probably aren't resolving correctly. Make sure dns and /etc/hosts are all correct along with resolv.conf and nsswitch.conf ----------------------------------------------------------------------------- --------------------------------------------------------------- Christopher L. Barnard [cbar44@tsg.cbot.com] Does the server use DNS to resolve hostnames? There is a 60 second timeout built into DNS. If the first server in the /etc/resolv.conf file does not respond within 60 seconds, resolution will pass to the next host on the list. Host resolution is used on login. Take a look at your /etc/nsswitch.conf file. If the hosts: line has dns first, make sure your /etc/resolv.conf file is correct. ----------------------------------------------------------------------------- ---------------------------------------------------------------- The only question I have with these responses is that I have another server that is almost identical (same network, netmask, resolv.conf, nsswitch.conf etc.) and it did not experience this issue, but there may be other variables. Other responses pointed to problems with NFS mounted file systems hanging things up (I should have mentioned that I am not having this problem), NFS mounted home directories, the quota command in /etc/profile (see below). Others mentioned to use "truss" to find the delay. I will have to look into this command. ----------------------------------------------------------------------------- ------------------------------------------------------------ Loris Serena [loris.serena@bt.com] Do you have "quota" enabled in /etc/profile? Try comment that line and see if that helps ----------------------------------------------------------------------------- -------------- Mads Vaagland [mads.vaagland@ntnu.no] I've seen similar behavor on solaris, due to the '/usr/sbin/quota'-command in /etc/profile. If you've got any nfs-mounts that are down, 'quota' may hang for some time, trying to check quotas on the remote filesystems. I'm not sure this is the source of your problem, but it's worth checking. --------------------------------------------------------------------- thank you all so much for your quick responces, it really does help, I need to respond more!! Eric Larkin UNIX System Administrator _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Dec 1 11:38:07 2005
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:53 EST