*** empty log message ***

tests/tail-2/tail-n0f

@@ -0,0 +1,51 @@
+#!/bin/sh
+# Make sure that `tail -n0 -f' and `tail -c0 -f' sleep
+# rather than doing what amounted to a busy-wait.
+# This bug was fixed for 5.0.91
+# It skips the test if your system lacks a /proc/$pid/status
+# file, or if its contents don't look right.
+
+if test "$VERBOSE" = yes; then
+  set -x
+  tail --version
+fi
+
+sleep 2 &
+pid=$!
+sleep .1
+grep '^State:[	 ]*[S]' /proc/$pid/status > /dev/null 2>&1 || \
+  {
+    echo "$0:/proc/$pid/status: missing or 'different': skipping this test" 1>&2
+    (exit 77); exit 77
+  }
+kill $pid
+
+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
+trap '(exit $?); exit $?' 1 2 13 15
+
+framework_failure=0
+mkdir -p $tmp || framework_failure=1
+cd $tmp || framework_failure=1
+touch empty || framework_failure=1
+echo anything > nonempty || framework_failure=1
+
+if test $framework_failure = 1; then
+  echo "$0: failure in testing framework" 1>&2
+  (exit 1); exit 1
+fi
+
+fail=0
+
+for file in empty nonempty; do
+  for c_or_n in c n; do
+    tail --sleep=4 -${c_or_n} 0 -f $file &
+    pid=$!
+    sleep .1
+    grep '^State:[	 ]*[S]' /proc/$pid/status > /dev/null || fail=1
+    kill $pid
+  done
+done
+
+(exit $fail); exit $fail