Add a test for this:

  When not interactive, don't prompt for a symlink.

1 files changed, 6 insertions, 5 deletions

diff --git a/tests/rm/dangling-symlink b/tests/rm/dangling-symlink
index 73cd889c7..ac0de5650 100755
--- a/tests/rm/dangling-symlink
+++ b/tests/rm/dangling-symlink
@@ -1,15 +1,14 @@
 #!/bin/sh
 # rm should not prompt before removing a dangling symlink.
-# But for fileutils-4.1.9, it would.
+# Likewise for a non-dangling symlink.
+# But for fileutils-4.1.9, it would do the former and
+# for fileutils-4.1.10 the latter.
 
 if test "$VERBOSE" = yes; then
   set -x
   rm --version
 fi
 
-# Make sure there's a tty on stdin.
-. $srcdir/../input-tty
-
 pwd=`pwd`
 t0=`echo "$0"|sed 's,.*/,,'`.tmp; tmp=$t0/$$
 trap 'status=$?; cd $pwd; chmod -R u+rwx $t0; rm -rf $t0 && exit $status' 0
@@ -19,6 +18,7 @@ framework_failure=0
 mkdir -p $tmp || framework_failure=1
 cd $tmp || framework_failure=1
 ln -s no-file dangle
+ln -s / symlink
 
 if test $framework_failure = 1; then
   echo '$0: failure in testing framework' 1>&2
@@ -27,7 +27,7 @@ fi
 
 fail=0
 
-rm dangle &
+rm --presume-input-tty dangle symlink &
 pid=$!
 # The buggy rm (fileutils-4.1.9) would hang here, waiting for input.
 
@@ -36,6 +36,7 @@ sleep 1
 
 # The file must no longer exist.
 ls -l dangle > /dev/null 2>&1 && fail=1
+ls -l symlink > /dev/null 2>&1 && fail=1
 
 kill $pid > /dev/null 2>&1