Re: SUSE 10.1 - any issues with grep recursion?
- From: Lawrence D'Oliveiro <ldo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Jun 2006 23:17:41 +1200
In article <AV_og.8$MV.1166@xxxxxxxxxxxxxx>,
bobmct <r.mariottiX@xxxxxxxxx> wrote:
The *.conf was the file(s) to look in for the SSLEngine string.[only top-level .conf files listed]
To verify what I am experiencing I've tried recursing with ls. Here are
some examples from my home machine running 10.1:
/etc/apache2> ls -1 -R *.conf
Even though I explicitly stated -R (Recurse) on the command line you can
notice that there was no recursion.
Because you didn't specify anything for it to recurse _into_. All the
items specified on the command line were files, not directories.
Now, here the results of the find command:[lots of .conf files, including those in subdirectories, listed]
/etc/apache2> find . -name "*.conf" -print
Now, have you noticed yet the extra item you specified on the second
command line, that you did not in the first? It was ".", the name of the
directory to recurse into.
Since you only wanted the grep to look at .conf files, and not
directories or any other files, you should have used it with find in the
first place:
find . -name '*.conf' -exec grep SSLEngine '{}' ';'
.
- References:
- SUSE 10.1 - any issues with grep recursion?
- From: bobmct
- Re: SUSE 10.1 - any issues with grep recursion?
- From: houghi
- Re: SUSE 10.1 - any issues with grep recursion?
- From: bobmct
- SUSE 10.1 - any issues with grep recursion?
- Prev by Date: Re: Ubuntu seems better than SuSE... still want to go back, though
- Next by Date: Re: Web-based remoting...
- Previous by thread: Re: SUSE 10.1 - any issues with grep recursion?
- Next by thread: Re: SUSE 10.1 - any issues with grep recursion?
- Index(es):
Relevant Pages
|