PROBLEM: (QAR 26710) (Patch ID: OSF405-400379) ******** The find -follow command does not detect previously visited directories properly. The system displays error messages similar to the following and gets caught in an infinite loop. For example: $ find /tmp/level1 -follow -print /tmp/level1 find: cannot open symbolic link < /tmp/level1/abc:: No such file or directory find: cannot open symbolic link < /tmp/level1/pass:: Not a directory /tmp/level1/level2 find: cannot open symbolic link < /tmp/level1/level2/pcap:: Not a directory find: cannot open symbolic link < /tmp/level1/level2/newname:: No such file or directory /tmp/level1/level2/magic /tmp/level1/level2/magic.old /tmp/level1/level2/level3 /tmp/level1/level2/level4 . (gets into an infinite loop) . Note, level3 is a subdirectory of level2 and is linked to level1. PROBLEM: (QAR 47329) (Patch ID: OSF405-400379) ******** The find -follow command does not correctly handle symbolic links. This can have the following symptoms: find /tmp/two -follow -print /tmp/two /tmp/two/second find: cannot open symbolic link < /tmp/two/second/pcap:: Not a directory /tmp/two/second/secondx /tmp/two/second/secondx/profile /tmp/two/second/secondx/protocols find: bad status-- /tmp/two/second/magic find: bad status-- /tmp/two/second/third find: bad status-- /tmp/two/secondx PROBLEM: (QAR 52307) (Patch ID: OSF405-400379) ******** The find -follow command goes into a loop when a symbolic link refers to an object in the parent of the search tree. For example: >cd /tmp >mkdir junk >cd junk >ln -s /tmp/junk child.link >ls child.link >find . -follow -print . ./child.link ./child.link/child.link ./child.link/child.link/child.link ./child.link/child.link/child.link/child.link ./child.link/child.link/child.link/child.link/child.link ./child.link/child.link/child.link/child.link/child.link/child.link ./child.link/child.link/child.link/child.link/child.link/child.link/child. PROBLEM: (QAR 19076) (Patch ID: OSF405-400379) ******** When cpio archives are created with the find command (find . -cpio ...), 'find' does not allow for extended attributes from the property list mechanism. PROBLEM: (QAR 44191) (Patch ID: OSF405-400379) ******** The find command produces incorrect output when the -prune and -depth primaries are used simultaneously. PROBLEM: (QAR 47432) (Patch ID: OSF405-400379) ******** The find command does not behave according to specification. A problem occurs when the search is restricted to a single file system. PROBLEM: (QAR 49857) (Patch ID: OSF405-400379) ******** The find . -fstype command does not report an error when given an unknown file system. For example: #prior to fix: $ find . -fstype banana -print $ #After fix: $ ./find . -fstype banana -print find: Unknown file system type banana. PROBLEM: (QAR 47223) (Patch ID: OSF405-400379) ******** The find command exits when it encounters a file system different from the file system on which it started. PROBLEM: (MCGM30XZ2) (Patch ID: OSF405-300) ******** This patch fixes the "find" command in which files in directories which were mounted with the "-fstype nfsv2" argument were not found.