blob: 7d9c96582c84ef90dfb99afc4fcf15153f340e24 (
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
|
#!/bin/sh
# This is a bit of a torture test for mkdir -p, too.
# GNU rm performs *much* better on systems that have a d_type member
# in the directory structure because then it does only one stat per
# command line argument.
# If this test takes too long on your system, blame the OS.
: ${RM=rm}
: ${MKDIR=mkdir}
test=deep-1
# Don't require use of TMPDIR.
: ${RM_TMPDIR=.}
if test "$VERBOSE" = yes; then
set -x
$RM --version
fi
umask 022
fail=0
tmp=$RM_TMPDIR/t-rm.$$
k20=/k/k/k/k/k/k/k/k/k/k/k/k/k/k/k/k/k/k/k/k
k200=$k20$k20$k20$k20$k20$k20$k20$k20$k20$k20
# Be careful not to exceed max file name length (usu 512?).
# Doing so wouldn't affect GNU mkdir or GNU rm, but any tool that
# operates on the full pathname (like `test') would choke.
k_deep=$k200$k200
# Create a directory in $tmp with lots of `k' components.
deep=$tmp$k_deep
echo 'creating a hierarchy 400 deep in $tmp...'
$MKDIR -p $deep || fail=1
find $tmp > k
# Make sure the deep dir was created.
test -d $deep || fail=1
$RM -r $tmp || fail=1
# Make sure all of $tmp was deleted.
test -d $tmp && fail=1
exit $fail
|
