From: Joerg Vehlow <lkml@jv-coder.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] ssh-stress: Convert to new api
Date: Tue, 15 Jun 2021 11:59:35 +0200 [thread overview]
Message-ID: <0324b896-0ef7-66d3-3d2c-9b9817721500@jv-coder.de> (raw)
In-Reply-To: <YMdgXPeTNHMtna/M@pevik>
Hi Petr,
On 6/14/2021 3:57 PM, Petr Vorel wrote:
>
>>> Out of curiosity, did you test this on Two Host Configuration [2] (i.e. ssh)?
>>> Or just netns?
>> No, but should have...
>> I found two major problems with the test (will send a v2). But apart from
>> that, either I was not able to find the documentation or it is not clear
>> enough to me, how to run the two host setup.
>> I found network/README.md, but it only mentions to set RHOST, but for my
>> setup (with ips different from the default ones, IPV{4,6}_{L,R}HOST is also
> Yes we should be more verbose at Two Host Configuration [1] as there is nothing
> more. At least to mention IPV{4,6}_{L,R}HOST.
+1
>> required) and ltp must already be in the PATH on rhost, which was not
>> possible for my rhost setup, where the filesystem is read-only and I had to
>> hack setting the path into tst_rhost_run. It is not totally clear, that ltp
> What exactly was your problem? Having to modify PATH on shell config on read
> only system? I'll send a proposal to set PATH in tst_test.sh.
The simplest way to set the path would be in .profile on the rhost, but
since the whole fs was readonly, this was not possible.
I somehow thought ltp would take care of setting the path and also
exporting LTPROOT automatically, because according to the documentation,
it expects to find ltp at the same path as on the LHOST.
Maybe this restriction could even be lifted, if the LHOST sets the paths
on the RHOST (something like RHOST_LTPROOT, which defaults to LTPROOT).
This could then be used to set PATH on RHOST as you suggested.
For my tests I just added "export PATH=$PATH;" to the rhost ssh command.
It wanted to use just "PATH=$PATH", but that did not work because I used
command grouping in the ssh-stress test.
"X=1 ( echo $X )" fails with a syntax error. With export it works and I
guess it should be implemented cleaner than just forcing the whole PATH
from the LHOST onto the RHOST as I did.
J?rg
prev parent reply other threads:[~2021-06-15 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 10:19 [LTP] [PATCH] ssh-stress: Convert to new api Joerg Vehlow
2021-06-14 7:14 ` Petr Vorel
2021-06-14 9:42 ` Joerg Vehlow
2021-06-14 13:57 ` Petr Vorel
2021-06-15 9:59 ` Joerg Vehlow [this message]
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=0324b896-0ef7-66d3-3d2c-9b9817721500@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.