我使用的方法是这样的:

find . -name <filename> -print0 | xargs -0 cat | grep <word2search4>

"find"的"-print0"参数和"xargs"的"-0"参数需要正确处理文件路径/名称中的空白。

列出并查看服务器上/ghi和/jkl目录下所有abc.def文件的内容

find /ghi /jkl -type f -name abc.def 2> /dev/null -exec ls {} \; -exec cat {} \;

要列出带有注释条目的abc.def文件并显示，请查看目录/ghi和/jkl中的这些条目

find /ghi /jkl -type f -name abc.def 2> /dev/null -exec grep -H ^# {} \;

有几种方法可以将find命令返回的文件列表传递给cat命令，但从技术上讲，并非所有方法都使用管道，也没有一种方法实际上直接通过管道传递给cat。

The simplest is to use backticks (`): cat `find [whatever]` This takes the output of find and effectively places it on the command line of cat. This doesn't work well if find has too much output (more than can fit on a command-line) or if the output has special characters (like spaces). In some shells, including bash, one can use $() instead of backticks : cat $(find [whatever]) This is less portable, but is nestable. Aside from that, it has pretty much the same caveats as backticks. Because running other commands on what was found is a common use for find, find has an -exec action which executes a command for each file it finds: find [whatever] -exec cat {} \; The {} is a placeholder for the filename, and the \; marks the end of the command (It's possible to have other actions after -exec.) This will run cat once for every single file rather than running a single instance of cat passing it multiple filenames which can be inefficient and might not have the behavior you want for some commands (though it's fine for cat). The syntax is also a awkward to type -- you need to escape the semicolon because semicolon is special to the shell! Some versions of find (most notably the GNU version) let you replace ; with + to use -exec's append mode to run fewer instances of cat: find [whatever] -exec cat {} + This will pass multiple filenames to each invocation of cat, which can be more efficient. Note that this is not guaranteed to use a single invocation, however. If the command line would be too long then the arguments are spread across multiple invocations of cat. For cat this is probably not a big deal, but for some other commands this may change the behavior in undesirable ways. On Linux systems, the command line length limit is quite large, so splitting into multiple invocations is quite rare compared to some other OSes. The classic/portable approach is to use xargs: find [whatever] | xargs cat xargs runs the command specified (cat, in this case), and adds arguments based on what it reads from stdin. Just like -exec with +, this will break up the command-line if necessary. That is, if find produces too much output, it'll run cat multiple times. As mentioned in the section about -exec earlier, there are some commands where this splitting may result in different behavior. Note that using xargs like this has issues with spaces in filenames, as xargs just uses whitespace as a delimiter. The most robust, portable, and efficient method also uses xargs: find [whatever] -print0 | xargs -0 cat The -print0 flag tells find to use \0 (null character) delimiters between filenames, and the -0 flag tells xargs to expect these \0 delimiters. This has pretty much identical behavior to the -exec...+ approach, though is more portable (but unfortunately more verbose).

对我来说，听起来像是shell脚本的工作:

for file in 'find -name *.xml'
do
   grep 'hello' file
done

或者类似的东西

我使用的方法是这样的:

find . -name <filename> -print0 | xargs -0 cat | grep <word2search4>

"find"的"-print0"参数和"xargs"的"-0"参数需要正确处理文件路径/名称中的空白。

使用ggrep。

ggrep -H -R -I "mysearchstring" *

在Unix中搜索包含位于当前目录或子目录中的文本的文件