|
Technically speaking...
find /mydir/*.java
_does_ recurse. It recurses into all directories that end with *.java.
But, since folks don't typically use that name for directories, it
/effectively/ stops recursion.
Hi Charles,
Two questions:
why doesn't the shell handle the wild card?
Depending on which example you're referring to... either the shell DOES
handle the wildcard, or it doesn't handle it because you escaped the
wildcard character.
If you want more detail, please show me the statement you're referring to...
Assuming I don't have and subdirectories that match the name, would
this bite me in some way?
find /mydir/????.fin.cis0000.staf.input01.????????.zip –exec rm {} \;
As Dennis pointed you, you really don't need to use 'find' for something
like this. The way you have it coded, it'll submit a new background job
for every file that matches your ???? expression. While that'll work,
it's rather inefficient.
You could do this instead:
rm /mydir/????.fin.cis0000.staf.input01.????????.zip
That'll accomplish the same thing, and will do it all in one job -- much
more efficient.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.