From ae5b4617fdbd4d3e0d933c1eac22f41e53365407 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= Date: Fri, 5 Nov 2021 12:39:09 +0100 Subject: tests: shell: README: $NFT does not have to be a path to a binary MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Since commit 7c8a44b25c22, $NFT can contain an arbitrary command, e.g. 'valgrind nft'. Fixes: 7c8a44b25c22 ("tests: shell: Allow wrappers to be passed as nft command") Signed-off-by: Štěpán Němec Signed-off-by: Phil Sutter --- tests/shell/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/shell') diff --git a/tests/shell/README b/tests/shell/README index 35f6e378..4dd595d9 100644 --- a/tests/shell/README +++ b/tests/shell/README @@ -21,7 +21,7 @@ And generate missing dump files with: Before each test file invocation, `nft flush ruleset' will be called. Also, test file process environment will include the variable $NFT -which contains the path to the nft binary being tested. +which contains the nft command being tested. You can pass an arbitrary $NFT value as well: # NFT=/usr/local/sbin/nft ./run-tests.sh -- cgit v1.2.3