Depending on what his find did, Chris may have encountered a bug. Find
/ or /etc -exec grep foo {} \; can hang on some versions of Solaris
because it encounters a named pipe and gets stuck grepping the pipe
forever.
This was one of my top 10 pet peeves when moving back to Solaris from
gnu/linux (don't worry, I had peeves moving the other direction too.)
Grepping pipes and the fact that Solaris's grep lacks the -r (recursive)
option needlessly complicates searching deep filesystems for a text
string. On a massive Sun box with multiple NFS mounted filesystems, you
probably avoid ever searching the entire filesystem tree, but most
GNU/Linux distributions make it easy for those with laptops and small (<
50G) partitions to search the entire tree in a finite amount of time.
Joerg Schilling wrote:
Chung Hang Christopher Chan <[EMAIL PROTECTED]> wrote:
I am not sure what you understan by this....
Try to use GNU find on a mounted CD and see that it
does
not find anything that is not in the root directory.
I was quite surprised about what was called 'bloat' in
'Slowlaris 8'.
There never was something like 'Slowlaris 8'
over 24 hours with no result versus seconds? That
command that was used will actually not run into
any
directories. queue/mess/* represents all the
directories find has to go look in.
It gives typically a speedup of 5x
I assure you that I feel far more differently about
this. This is not a mere 5x speedup. 24 hours versus
say one minute is already way beyond 5x.
It depends on the balance between the number of directories
and the number of files in them.
24 hours sounds unreasonable. What kind of FS is this?
Jörg
_______________________________________________
opensolaris-discuss mailing list
[email protected]
