shell while内获取外部变量内容

一、问题

问题很简单,看下面一段tmp.sh代码:

#!/bin/sh
x="this is the initial value of x"
cat /tmp/tmp | while read line;do
        x="$line"
        echo $x
done
echo x = $x

/tmp/tmp的内容

1,a

执行 ./tmp.sh,正常x变量是蓝色的“1,a”,但是实际的结果却是红色部分:

[[email protected] ~]$ ./tmp.sh 
1,a
x = this is the initial value of x

问题很明显,变量x在while内修改之后,并没有带到外面来,为什么哪?

二、答案

经过几经查找,终于发现问题的原因:是因为启动了子进程,而变量x在子进程修改之后,并没有带入到父进程。原文如下:

This is because in the Bourne shell redirected control structures run in a subshell, so the value of x only gets changed in the  subshell, and is lost when the loop ends.

In other shells the same result may be seen because of the way pipelines are handled. In shells other than ksh (not pdksh) and zsh elements of a pipeline are run in subshells. In ksh and zsh, the last element of the pipeline is run in the current shell.

An alternative for non-Bourne shells is to use redirection
instead of the pipeline

如何解决哪?

1、一般方法:

#!/bin/sh
x="this is the initial value of x"
while read line;do
        x="$line"
        echo $x
done < /tmp/tmp
echo x = $x

运行:

[qiu.li@l-tdata1.tkt.cn6 ~]$ ./tmp.sh 
1,a
x = 1,a

2、优雅一些的解决方法:

#!/bin/sh
x="this is the initial value of x"
exec 3<&0         # save stdin
exec < /tmp/tmp
while read line; do
        x=$line
        echo $x
done
exec 0<&3        # restore stdin
echo x = $x

本人英文实在有限,原因只能贴出英文:

Note that putting #!/bin/sh at the top of a script doesn‘t  guarantee you‘re using the Bourne shell. Some systems link /bin/sh  to some other shell. Check your system documentation to find out what shell you‘re really getting in this case.

大概是说: 注意最上面的#!/bin/sh 如果使用其他的此脚本不能运行。但是在有些系统/bin/sh 被指定到了其他的shell解释器里面,也是出现不一样的结果。详细的参考:http://www.cnblogs.com/liqiu/p/4107948.html

郑重声明:本站内容如果来自互联网及其他传播媒体,其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享,并不代表本站赞同其观点和对其真实性负责,也不构成任何其他建议。