Python subprocess.call 多次调用的奇怪行为
我正在尝试使用这样的 subprocess.call 函数调用远程（ssh）命令。
import shlex
from subprocess import call
cmd1='ssh [email protected] mkdir temp'
cmd2='scp test.txt [email protected]:temp'
call(shlex.split(cmd1))
call(shlex.split(cmd2))
当我调用上面的方法时， mkdir 似乎没有执行 - 尽管 subprocess.call 的文档说它在返回之前等待执行。各个 ssh 调用的延迟约为 0.5 秒。它似乎在千兆位 LAN 上工作得很好，延迟几乎为零。
然而，当像这样进行调用时，它似乎工作正常：
call(shlex.split(cmd1)) & call(shlex.split(cmd2))
第一种方法有什么问题？
谢谢你， 米莉安娜
I am trying to call remote (ssh) commands using the subprocess.call function like this.
import shlex
from subprocess import call
cmd1='ssh [email protected] mkdir temp'
cmd2='scp test.txt [email protected]:temp'
call(shlex.split(cmd1))
call(shlex.split(cmd2))
When I call the above, the mkdir does not seem to execute - although the documentation for subprocess.call says it waits for execution before returning. The latency of the individual ssh calls is about 0.5 seconds. It seems to work fine on the gigabit LAN where the latency is almost zero.
However it seems to work fine when the calls are made like this:
call(shlex.split(cmd1)) & call(shlex.split(cmd2))
What is the problem with the first approach?
Thank you,
Miliana
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看来您没有在第一个方法中查找调用的结果。
It looks like you don't look for the result of call in the first method.
你的有问题的版本总是对我有用。我认为这是一个网络问题，特别是因为您指出它可以在千兆位局域网中工作。
Your problematic version always works for me. I would think this is a network problem especially since you indicate that it works in gigabit LANs.