From: Štěpán Němec Date: Fri, 5 Nov 2021 11:39:09 +0000 (+0100) Subject: tests: shell: README: $NFT does not have to be a path to a binary X-Git-Tag: v1.0.1~21 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ae5b4617fdbd4d3e0d933c1eac22f41e53365407;p=thirdparty%2Fnftables.git tests: shell: README: $NFT does not have to be a path to a binary 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 --- 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