From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V2] fix scp error on FreeBSD
Date: Tue, 25 Oct 2016 14:47:58 +0800 [thread overview]
Message-ID: <1477378078-2865-1-git-send-email-gangx.xu@intel.com> (raw)
when scp something to FreeBSD the prompt is different with other
ex:FreeBSD is "Password for root@freeBSD:"
Fedora is "root@xx.xxx.xxx.xxx's password:"
Signed-off-by: xu,gang <gangx.xu@intel.com>
---
framework/ssh_pexpect.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/framework/ssh_pexpect.py b/framework/ssh_pexpect.py
index 1abf8a1..9668daf 100644
--- a/framework/ssh_pexpect.py
+++ b/framework/ssh_pexpect.py
@@ -176,11 +176,11 @@ class SSHPexpect(object):
p = pexpect.spawn(scp_cmd)
time.sleep(0.5)
ssh_newkey = 'Are you sure you want to continue connecting'
- i = p.expect([ssh_newkey, 'password: ', "# ", pexpect.EOF,
+ i = p.expect([ssh_newkey, '[pP]ssword', "# ", pexpect.EOF,
pexpect.TIMEOUT], 120)
if i == 0: # add once in trust list
p.sendline('yes')
- i = p.expect([ssh_newkey, '[pP]assword: ', pexpect.EOF], 2)
+ i = p.expect([ssh_newkey, '[pP]ssword', pexpect.EOF], 2)
if i == 1:
time.sleep(0.5)
--
1.9.3
next reply other threads:[~2016-10-25 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 6:47 xu,gang [this message]
2016-10-26 7:41 ` Liu, Yong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1477378078-2865-1-git-send-email-gangx.xu@intel.com \
--to=gangx.xu@intel.com \
--cc=dts@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).