Use "eval" in history_002_pos for log_must

Otherwise the output is consumed by the output redirection.

Reviewed-by: Serapheim Dimitropoulos <serapheim@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Tim Chase <tim@chase2k.com>
Closes #7570

diff --git a/tests/zfs-tests/tests/functional/history/history_002_pos.ksh b/tests/zfs-tests/tests/functional/history/history_002_pos.ksh
index 979f06076ade4e6f100880c40a166621cb8bfd66..af69668fb8765e4f7f5bad8164e3b738dceaa465 100755 (executable)
--- a/tests/zfs-tests/tests/functional/history/history_002_pos.ksh
+++ b/tests/zfs-tests/tests/functional/history/history_002_pos.ksh
@@ -143,8 +143,8 @@ run_and_verify "zfs snapshot $fssnap2"
 run_and_verify "zfs snapshot $volsnap2"
 
 # Send isn't logged...
-log_must zfs send -i $fssnap $fssnap2 > $tmpfile
-log_must zfs send -i $volsnap $volsnap2 > $tmpfile2
+log_must eval "zfs send -i $fssnap $fssnap2 > $tmpfile"
+log_must eval "zfs send -i $volsnap $volsnap2 > $tmpfile2"
 # Verify that's true
 zpool history $TESTPOOL | grep 'zfs send' >/dev/null 2>&1 && \
     log_fail "'zfs send' found in history of \"$TESTPOOL\""