Many thanks to
Qureshi, Malahat <MQureshi@allstate.com>
Neal S. Pressman <firstname.lastname@example.org>
Renny Koshy <email@example.com>
I must specially thanks Viet_Q_Hoang and I included
his reply below.
That sounds like a symptom of some nfs/automounting
Easiest way to track it down is to run 'find / -print'
where it hangs.
It hung at /xfn. Comment out /xfn in auto_master and
autofs. everything works fine now.
> -----Original Message-----
> From: sun unix [mailto:firstname.lastname@example.org]
> Sent: Friday, May 26, 2000 12:21 PM
> To: Sun Managers
> Subject: find hung in Solaris 2.6 and 7
> Dear Sun Managers,
> I've an E10k and have 5x 9.1 G disks. Each hard disk
> is mounted as a separate file system. NFS is not
> running in this machine. My problem is I have a
> that consists a find command that run well in
> 2.5.1. However, when I run the same script on
> 2.6 or 7, it doesn't work.
> I then run the find command manually in command
> find / -name .profile -print.
> To my surprise, after finding the .profile file in a
> few file systems, it just hung there. I waited a few
> hours but the find doesn't terminate. When I do a
> on the process, it is giving me the process is in
> I never see such a thing before and by
> right after finding the file in all the file
> it should exit and go back to the command prompt.
> I did the find in each separate file system, it
> fine and exits.
> e.g. # find /a -name .profile -print
> # find /b -name .profile -print
> # find /c -name .profile -print
> Can someone shed some light on it. I had searched
> the archive and someone mentioned that there is a
> different in find command btw Solaris 2.5.1 and
> Solaris 2.6. But the summary doesn't help in my
> case. Would highly appreciate any help and what
> are the things I need to investigate further.
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:08 CDT