From c0c8b300eb670905e569518442f16f2c7966a51b Mon Sep 17 00:00:00 2001 From: Arushi Singhal Date: Sun, 1 Jul 2018 11:36:09 +0530 Subject: nftables: tests: shell: Replace "%" with "#" or "$" Shell prompt ends with: "%", indicates a C shell. "$", indicates shell that's compatible with the Bash. "#", indicates shell is running as the system's root. So, "%" is replaced with "$" or "#". Signed-off-by: Arushi Singhal Signed-off-by: Florian Westphal --- tests/shell/README | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'tests/shell/README') diff --git a/tests/shell/README b/tests/shell/README index e6d83bce..e0279bbd 100644 --- a/tests/shell/README +++ b/tests/shell/README @@ -5,24 +5,24 @@ It can run arbitrary executables which can perform any test apart of testing the nft syntax or netlink code (which is what the regression tests does). To run the test suite (as root): - % cd tests/shell - % ./run-tests.sh + $ cd tests/shell + # ./run-tests.sh Test files are executables files with the pattern <>, where N is the expected return code of the executable. Since they are located with `find', test-files can be spread in any sub-directories. You can turn on a verbose execution by calling: - % ./run-tests.sh -v + # ./run-tests.sh -v And generate missing dump files with: - % ./run-tests.sh -g + # ./run-tests.sh -g Before each call to the test-files, `nft flush ruleset' will be called. Also, test-files will receive the environment variable $NFT which contains the path to the nftables binary being tested. You can pass an arbitrary $NFT value as well: - % NFT=/usr/local/sbin/nft ./run-tests.sh + # NFT=/usr/local/sbin/nft ./run-tests.sh By default the tests are run with the nft binary at '../../src/nft' -- cgit v1.2.3