Finger always return 0 with bad user and host test. And it also return
different error message on different distros. So let's only check stderr
message and decide whether the test pass or fail.
Signed-off-by: Hangbin Liu <liuhang...@gmail.com>
---
testcases/network/tcp_cmds/finger/finger01 | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/testcases/network/tcp_cmds/finger/finger01
b/testcases/network/tcp_cmds/finger/finger01
index 203d746..e01c1ad 100755
--- a/testcases/network/tcp_cmds/finger/finger01
+++ b/testcases/network/tcp_cmds/finger/finger01
@@ -112,14 +112,13 @@ do_test2()
BADHOST="xxxx"
tst_resm TINFO "finger -badflag default "
- finger -x 2>&1 1>/dev/null && end_testcase "finger -x should fail"
+ finger -x &>/dev/null && end_testcase "finger -x should fail"
tst_resm TINFO "finger -bad user "
- finger $BADUSER 2>&1 1>/dev/null || end_testcase "finger $BADUSER"
- finger @$BADHOST 2>&1 1>/dev/null | grep "finger: unknown host" \
- || end_testcase "finger @$BADHOST"
- if ! finger $BADUSER@$BADHOST 2>&1 1>/dev/null \
- | grep "finger: unknown host"; then
+ [ "$(finger $BADUSER 2>&1 1>/dev/null)" ] || end_testcase "finger $BADUSER"
+ [ "$(finger @$BADHOST 2>&1 1>/dev/null)" ] || \
+ end_testcase "finger $BADUSER@$BADHOST"
+ [ "finger $BADUSER@$BADHOST 2>&1 1>/dev/null" ] || \
end_testcase "finger $BADUSER@$BADHOST"
fi
}
--
1.9.3
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
