site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Apr 6, 2005, at 11:26 AM, Charles Jolley wrote: Hi: -Shawn _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I have a little command line utility that scans through some files, calling fstat on each of them. The problem is when I test this with a large number of files (about 180,000), I start having problems thoughout my system while the scan in running. Copying files in the Finder will sometimes fail; apps will die while accessing files and so on. Even the scanner's stat calls will failnow and then. I suspect the problem is that my scanner is exhausting the file caches or something like that causing file system calls to fail. But I'm not sure. Has anyone else run into this kind of problem? Do you know why a tight loop calling fstat on files would be causing this problem? What is the best way to fix this? Also what file systems types (local or remote?) and version of Mac OS X are involved? This email sent to site_archiver@lists.apple.com