In addition to the fairly common forms of input/output redirection the shell recognizes something called process substitution. Although not documented as a form of input/output redirection, its syntax and its effects are similar.
The syntax for process substitution is:
<(list)
or
>(list)
where each
list is a command or a pipeline of commands. The effect of process substitution is to make each list act like a file. This is done by giving the list a
name in the file system and then substituting that name in the command line. The list is given a name either by connecting the list to named pipe or by using a file in
/dev/fd (if supported by the O/S). By doing this, the command simply sees a file name and is unaware that its reading from or writing to a command pipeline.
To substitute a command pipeline for an input file the syntax is:
command ... <(list) ...
To substitute a command pipeline for an output file the syntax is:
command ... >(list) ...
At first process substitution may seem rather pointless, for example you might imagine something simple like:
uniq <(sort a)
to sort a file and then find the unique lines in it, but this is more commonly (and more conveniently) written as:
sort a | uniq
The power of process substitution comes when you have multiple command pipelines that you want to connect to a single command.
For example, given the two files:
# cat a
e
d
c
b
a
# cat b
g
f
e
d
c
b
To view the lines unique to each of these two unsorted files you might do something like this:
# sort a | uniq >tmp1
# sort b | uniq >tmp2
# comm -3 tmp1 tmp2
a
f
g
# rm tmp1 tmp2
With process substitution we can do all this with one line:
# comm -3 <(sort a | uniq) <(sort b | uniq)
a
f
g
Depending on your shell settings you may get an error message similar to:
syntax error near unexpected token `('
when you try to use process substitution, particularly if you try to use it within a shell script. Process substitution is not a POSIX compliant feature and so it may have to be enabled via:
set +o posix
Be careful not to try something like:
if [[ $use_process_substitution -eq 1 ]]; then
set +o posix
comm -3 <(sort a | uniq) <(sort b | uniq)
fi
The command
set +o posix enables not only the execution of process substitution but the recognition of the syntax. So, in the example above the shell tries to parse the process substitution syntax before the "set" command is executed and therefore still sees the process substitution syntax as illegal.
Of course, note that all shells may not support process substitution, these examples will work with bash.
進(jìn)程替換與命令替換很相似. 命令替換把一個(gè)命令的結(jié)果賦值給一個(gè)變量, 比如dir_contents=`ls -
al`或xref=$( grep word datafile). 進(jìn)程替換把一個(gè)進(jìn)程的輸出提供給另一個(gè)進(jìn)程(換句話說(shuō), 它把
一個(gè)命令的結(jié)果發(fā)給了另一個(gè)命令).
命令替換的模版
用圓括號(hào)擴(kuò)起來(lái)的命令
>(command)
<(command)
啟動(dòng)進(jìn)程替換. 它使用/dev/fd/<n>文件將圓括號(hào)中的進(jìn)程處理結(jié)果發(fā)送給另一個(gè)進(jìn)程. [1] (譯
者注: 實(shí)際上現(xiàn)代的UNIX類操作系統(tǒng)提供的/dev/fd/n文件是與文件描述符相關(guān)的, 整數(shù)n指的就
是進(jìn)程運(yùn)行時(shí)對(duì)應(yīng)數(shù)字的文件描述符)
在"<"或">"與圓括號(hào)之間是沒(méi)有空格的. 如果加了空格, 會(huì)產(chǎn)生錯(cuò)誤.
bash$ echo >(true)
/dev/fd/63
bash$ echo <(true)
/dev/fd/63
Bash在兩個(gè)文件描述符之間創(chuàng)建了一個(gè)管道, --fIn和fOut--. true命令的stdin被連接到fOut
(dup2(fOut, 0)), 然后Bash把/dev/fd/fIn作為參數(shù)傳給echo. 如果系統(tǒng)缺乏/dev/fd/<n>文件, Bash會(huì)
使用臨時(shí)文件. (感謝, S.C.)
進(jìn)程替換可以比較兩個(gè)不同命令的輸出, 甚至能夠比較同一個(gè)命令不同選項(xiàng)情況下的輸出.
bash$ comm <(ls -l) <(ls -al)
total 12
-rw-rw-r-- 1 bozo bozo 78 Mar 10 12:58 File0
-rw-rw-r-- 1 bozo bozo 42 Mar 10 12:58 File2
-rw-rw-r-- 1 bozo bozo 103 Mar 10 12:58 t2.sh
total 20
drwxrwxrwx 2 bozo bozo 4096 Mar 10 18:10 .
drwx------ 72 bozo bozo 4096 Mar 10 17:58 ..
-rw-rw-r-- 1 bozo bozo 78 Mar 10 12:58 File0
-rw-rw-r-- 1 bozo bozo 42 Mar 10 12:58 File2
-rw-rw-r-- 1 bozo bozo 103 Mar 10 12:58 t2.sh
使用進(jìn)程替換來(lái)比較兩個(gè)不同目錄的內(nèi)容(可以查看哪些文件名相同, 哪些文件名不同):
1 diff <(ls $first_directory) <(ls $second_directory)
一些進(jìn)程替換的其他用法與技巧:
1 cat <(ls -l)
2 # 等價(jià)于 ls -l | cat
3
4 sort -k 9 <(ls -l /bin) <(ls -l /usr/bin) <(ls -l /usr/X11R6/bin)
5 # 列出系統(tǒng)3個(gè)主要'bin'目錄中的所有文件, 并且按文件名進(jìn)行排序.
6 # 注意是3個(gè)(查一下, 上面就3個(gè)圓括號(hào))明顯不同的命令輸出傳遞給'sort'.
7
8
9 diff <(command1) <(command2) # 給出兩個(gè)命令輸出的不同之處.
10
11 tar cf >(bzip2 -c > file.tar.bz2) $directory_name
12 # 調(diào)用"tar cf /dev/fd/?? $directory_name", 和"bzip2 -c > file.tar.bz2".
13 #
14 # 因?yàn)?dev/fd/<n>的系統(tǒng)屬性,
15 # 所以兩個(gè)命令之間的管道不必被命名.
16 #
17 # 這種效果可以被模擬出來(lái).
18 #
19 bzip2 -c < pipe > file.tar.bz2&
20 tar cf pipe $directory_name
21 rm pipe
22 # 或
23 exec 3>&1
24 tar cf /dev/fd/4 $directory_name 4>&1 >&3 3>&- | bzip2 -c > file.tar.bz2 3>&-
25 exec 3>&-
26
27
28 # 感謝, Stephane Chazelas
一個(gè)讀者給我發(fā)了一個(gè)有趣的例子, 是關(guān)于進(jìn)程替換的, 如下.
1 # 摘自SuSE發(fā)行版中的代碼片斷:
2
3 while read des what mask iface; do
4 # 這里省略了一些命令...
5 done < <(route -n)
6
7
8 # 為了測(cè)試它, 我們讓它做點(diǎn)事.
9 while read des what mask iface; do
10 echo $des $what $mask $iface
11 done < <(route -n)
12
13 # 輸出:
14 # Kernel IP routing table
15 # Destination Gateway Genmask Flags Metric Ref Use Iface
16 # 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
17
18
19
20 # 就像Stephane Chazelas所給出的那樣, 一個(gè)更容易理解的等價(jià)代碼是:
21 route -n |
22 while read des what mask iface; do # 管道的輸出被賦值給了變量.
23 echo $des $what $mask $iface
24 done # 這將產(chǎn)生出與上邊相同的輸出.
25 # 然而, Ulrich Gayer指出 . . .
26 #+ 這個(gè)簡(jiǎn)單的等價(jià)版本在while循環(huán)中使用了一個(gè)子shell,
27 #+ 因此當(dāng)管道結(jié)束后, 變量就消失了.
28
29
30
31 # 更進(jìn)一步, Filip Moritz解釋了上面兩個(gè)例子之間存在一個(gè)細(xì)微的不同之處,
32 #+ 如下所示.
33
34 (
35 route -n | while read x; do ((y++)); done
36 echo $y # $y 仍然沒(méi)有被聲明或設(shè)置
37
38 while read x; do ((y++)); done < <(route -n)
39 echo $y # $y 的值為route -n的輸出行數(shù).
40 )
41
42 # 一般來(lái)說(shuō), (譯者注: 原書作者在這里并未加注釋符號(hào)"#", 應(yīng)該是筆誤)
43 (
44 : | x=x
45 # 看上去是啟動(dòng)了一個(gè)子shell
46 : | ( x=x )
47 # 但
48 x=x < <(:)
49 # 其實(shí)不是
50 )
51
52 # 當(dāng)你要解析csv或類似東西的時(shí)侯, 這非常有用.
53 # 事實(shí)上, 這就是SuSE的這個(gè)代碼片斷所要實(shí)現(xiàn)的功能.
注意事項(xiàng)
[1] 這與命名管道(臨時(shí)文件)具有相同的作用, 并且, 事實(shí)上, 命名管道也被同時(shí)使用在進(jìn)程
替換中.