1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
#!/bin/sh
# Use du to exercise a corner of fts's FTS_LOGICAL code.
# Show that du fails with ELOOP (Too many levels of symbolic links)
# when it encounters that condition.
if test "$VERBOSE" = yes; then
set -x
du --version
fi
. $srcdir/../lang-default
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
# Create lots of directories, each containing a single symlink
# pointing at the next directory in the list.
# This number should be larger than the number of symlinks allowed in
# file name resolution, but not too large as a number of entries
# in a single directory.
n=400
dir_list=`seq $n`
mkdir $dir_list || framework_failure=1
for i in $dir_list; do
ip1=`expr $i + 1`
ln -s ../$ip1 $i/s || framework_failure=1
done
echo foo > $ip1
if test $framework_failure = 1; then
echo "$0: failure in testing framework" 1>&2
(exit 1); exit 1
fi
# If a system can handle this many symlinks in a file name,
# just skip this test.
file=1`printf %${n}s ' '|sed 's, ,/s,g'`
cat $file > /dev/null 2>&1 && \
{
cat <<EOF >&2
$0: Your systems appears to be able to handle more than $n symlinks
in file name resolution, so skipping this test.
EOF
(exit 77); exit 77
}
fail=0
# With coreutils-5.93 there was no failure.
# With coreutils-5.94 we get a diagnostic like this:
# du: cannot access `1/s/s/s/.../s': Too many levels of symbolic links
du -L 1 > /dev/null 2> out1 && fail=1
sed "s,1/s/s/s/[/s]*','," out1 > out || fail=1
cat <<\EOF > exp || fail=1
du: cannot access `': Too many levels of symbolic links
EOF
cmp out exp || fail=1
test $fail = 1 && diff out exp 2> /dev/null
(exit $fail); exit $fail
|
