blob: 31aac1fe5f1d4f4819a20a25b02af91e8d8230cc (
plain)
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
70
71
72
73
74
75
76
77
|
#!/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.
# Copyright (C) 2006-2008 Free Software Foundation, Inc.
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
if test "$VERBOSE" = yes; then
set -x
du --version
fi
. $srcdir/test-lib.sh
# 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
file=1
i_minus_1=0
for i in $dir_list `expr $n + 1`; do
case $i_minus_1 in
0) ;;
*)
ln -s ../$i $i_minus_1/s || framework_failure
file=$file/s;;
esac
i_minus_1=$i
done
echo foo > $i
# If a system can handle this many symlinks in a file name,
# just skip this test.
# The following also serves to record in `err' the string
# corresponding to strerror (ELOOP). This is necessary because while
# Linux/libc gives `Too many levels of symbolic links', Solaris
# renders it as `Number of symbolic links encountered during path
# name traversal exceeds MAXSYMLINKS'.
cat $file > /dev/null 2> err &&
skip_test_ 'Your system appears to be able to handle more than $n symlinks
in file name resolution'
too_many=`sed 's/.*: //' err`
fail=0
# With coreutils-5.93 there was no failure.
# With coreutils-5.94 we get the desired diagnostic:
# 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
echo "du: cannot access: $too_many" > exp || fail=1
compare out exp || fail=1
(exit $fail); exit $fail
|
