From: Petr Vorel <pvorel@suse.cz>
To: Akihiko Odaki <akihiko.odaki@daynix.com>,
ltp@lists.linux.it, Yan Vugenfirer <yan@daynix.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>
Subject: Re: [LTP] [PATCH 1/6] ftp/ftp01: Use tst_net.sh
Date: Fri, 21 Oct 2022 08:22:51 +0200 [thread overview]
Message-ID: <Y1I6u1a7RAS1wmZL@pevik> (raw)
In-Reply-To: <Y1GWOPpb+Z8hwhQd@pevik>
Hi Akihiko,
I'm sorry I overlooked your message at v1
https://lore.kernel.org/ltp/9894db50-6319-a818-c995-3ba9ab102c4b@daynix.com/
I guess script expects $PASSWD to be set.
Also trying to follow the instruction, none of them (allowing root in
/etc/ftpusers or filling /root/.netrc with machine localhost) work for me:
https://github.com/linux-test-project/ltp/tree/master/testcases/network#ftp-and-telnet-setup
I suppose any ftpd implementation must be run on the remote server (localhost,
if tst_net.sh uses netns - the default or on remote host, if ssh is used).
Otherwise ftp command "user $RUSER $PASSWD" cannot work, right?
Although it should behave the same regardless netns or ssh is used,
how do you test v3, with ssh or with netns (the default)? Or both?
It'd be nice if there was connection detection in the setup and tst_brk TCONF if
login does not work. The best would be to have configuration in the setup() +
cleanup in the cleanup()).
There are tests, which do vsftpd configuration: ftp-download-stress.sh,
ftp-upload-stress.sh.
BTW in the past we seriously considered to delete these highlevel smoke tests.
LTP is concentrated to test kernel API and internals, thus we didn't see much
value with smoke tests like this (that's why they haven't been rewritten to use
new API), specially if they require complex setup and get false positives when
SUT not configured properly. That's why it'd be nice to at least TCONF (if not
doing whole setup).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-10-21 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 12:07 [LTP] [PATCH 1/6] ftp/ftp01: Use tst_net.sh Akihiko Odaki
2022-10-20 12:07 ` [LTP] [PATCH 2/6] ftp/ftp01: Remove verbose comments Akihiko Odaki
2022-10-20 12:07 ` [LTP] [PATCH 3/6] ftp/ftp01: Remove old-style command substitution Akihiko Odaki
2022-10-20 12:07 ` [LTP] [PATCH 4/6] ftp/ftp01: Remove sleep option Akihiko Odaki
2022-10-20 12:07 ` [LTP] [PATCH 5/6] ftp/ftp01: Make variables local Akihiko Odaki
2022-10-20 12:07 ` [LTP] [PATCH 6/6] ftp/ftp01: Split the test function Akihiko Odaki
2022-10-20 18:40 ` [LTP] [PATCH 1/6] ftp/ftp01: Use tst_net.sh Petr Vorel
2022-10-21 6:22 ` Petr Vorel [this message]
2022-10-22 2:49 ` Akihiko Odaki
2022-10-24 9:46 ` Petr Vorel
2022-10-24 10:18 ` Petr Vorel
2022-10-26 19:22 ` Akihiko Odaki
2022-10-26 20:47 ` Petr Vorel
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=Y1I6u1a7RAS1wmZL@pevik \
--to=pvorel@suse.cz \
--cc=akihiko.odaki@daynix.com \
--cc=ltp@lists.linux.it \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.com \
/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