----Original Message---- >From: skilover >Sent: 21 April 2005 16:14 Hi Chuck! Hope you didn't mean to take this off-list deliberately, because I've added the list back in. Apologies in advance if you feel this was a deeply personal communication I shouldn't have shared with the world!
> Dave Korn wrote: >> ----Original Message---- >>> From: Chuck >>> Sent: 19 April 2005 16:09 >>> Findutils is broken when it comes to using it on the /proc filesystem. >>> The last version that worked is 4.1.7. Newer versions crash if you run >>> "find /proc". Anyone care to tackle this? >> Cannot reproduce: >> >> [EMAIL PROTECTED] /proc> find /proc >> /proc >> /proc/loadavg >> /proc/meminfo >> /proc/registry >> /proc/registry/HKEY_CLASSES_ROOT >> /proc/registry/HKEY_CLASSES_ROOT/* >> /proc/registry/HKEY_CLASSES_ROOT/*/OpenWithList >> find: /proc/registry/HKEY_CLASSES_ROOT/*/OpenWithList: Is a directory >> /proc/registry/HKEY_CLASSES_ROOT/*/shellex >> find: /proc/registry/HKEY_CLASSES_ROOT/*/shellex: Is a directory >> /proc/registry/HKEY_CLASSES_ROOT/*/InfoTip >> /proc/registry/HKEY_CLASSES_ROOT/*/QuickTip >> /proc/registry/HKEY_CLASSES_ROOT/*/AlwaysShowExt >> /proc/registry/HKEY_CLASSES_ROOT/*/TileInfo >> find: /proc/registry/HKEY_CLASSES_ROOT/*: Is a directory > Check your exit code from find. Mine stops in exactly the same place with > an exit code of 1. > > Perhaps I shouldn't have said it "crashes", but it definitely does not > traverse the entire registry. Ah. No, you absolutely shouldn't say it "crashes", because it does not "crash". Misdescribing a bug is the slowest imaginable way of getting it fixed! Particularly so in this case, because I don't see why find *shouldn't* return an exit code of 1 when it's had all those errors. Have you read "man find"? EXIT STATUS find exits with status 0 if all files are processed successfully, greater than 0 if errors occur. Presumably the reason that this behaviour is new is that there used to be a bug that stopped it even attempting to recurse those dirs, because nothing with '*' in it could ever be a valid filename. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/