From 1dc343bb3aaf2b47604a10004c70fb8f7c30ed84 Mon Sep 17 00:00:00 2001
From: Jim Meyering <jim@meyering.net>
Date: Sun, 14 Nov 2004 00:40:03 +0000
Subject: [PATCH] *** empty log message ***

---
 tests/misc/close-stdout | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/tests/misc/close-stdout b/tests/misc/close-stdout
index fc92da6517..4bdbbcb1db 100755
--- a/tests/misc/close-stdout
+++ b/tests/misc/close-stdout
@@ -1,5 +1,6 @@
 #!/bin/sh
 # Ensure that several programs work fine, even with stdout initially closed.
+# This is effectively a test of closeout.c's close_stdout function.
 
 if test "$VERBOSE" = yes; then
   set -x
@@ -23,6 +24,9 @@ fi
 PATH="$pwd/../..:$PATH"
 export PATH
 
+fail=0
+
+# Ensure these exit successfully, even though stdout is closed.
 touch a
 cp a b >&- || fail=1
 test -f b || fail=1
@@ -37,4 +41,8 @@ sleep 0 >&- || fail=1
 $pwd/../../src/true >&- || fail=1
 $pwd/../../src/printf '' >&- || fail=1
 
+# Ensure these fail, because stdout is closed.
+$pwd/../../src/printf 'foo' >&- 2>/dev/null && fail=1
+cp --verbose a b >&- 2>/dev/null && fail=1
+
 (exit $fail); exit $fail
-- 
2.47.2