3 # Copyright (C) 2001 by Martin Pool <mbp@samba.org>
5 # General-purpose test functions for rsync.
7 # This program is free software; you can redistribute it and/or modify
8 # it under the terms of the GNU General Public License version
9 # 2 as published by the Free Software Foundation.
11 # This program is distributed in the hope that it will be useful, but
12 # WITHOUT ANY WARRANTY; without even the implied warranty of
13 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
14 # Lesser General Public License for more details.
16 # You should have received a copy of the GNU Lesser General Public
17 # License along with this program; if not, write to the Free Software
18 # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
22 fromdir="$tmpdir/from"
29 if diff -u "$srcdir/testsuite/rsync.fns" "$srcdir/testsuite/rsync.fns" >/dev/null 2>&1; then
36 echo $ECHO_N "Test $1: $ECHO_C"
42 echo "$ECHO_T failed!"
53 find "$@" -print | sort | xargs "$TOOLDIR/tls"
62 # Build test directories $todir and $fromdir, with $fromdir full of files.
65 # Clean before creation
69 [ -d "$tmpdir" ] || mkdir "$tmpdir"
70 [ -d "$fromdir" ] || mkdir "$fromdir"
71 [ -d "$todir" ] || mkdir "$todir"
73 # On some BSD systems, the umask affects the mode of created
74 # symlinks, even though the mode apparently has no effect on how
75 # the links behave in the future, and it cannot be changed using
76 # chmod! rsync always sets its umask to 000 so that it can
77 # accurately recreate permissions, but this script is probably run
78 # with a different umask.
80 # This causes a little problem that "ls -l" of the two will not be
81 # the same. So, we need to set our umask before doing any creations.
84 touch "$fromdir/empty"
85 mkdir "$fromdir/emptydir"
87 # a hundred lines of text or so
88 rsync_ls_lR "$srcdir" > "$fromdir/filelist"
90 echo $ECHO_N "This file has no trailing lf$ECHO_C" > "$fromdir/nolf"
92 ln -s nolf "$fromdir/nolf-symlink"
95 cat $srcdir/*.c > "$fromdir/text"
97 cp "$fromdir/text" "$fromdir/dir"
98 mkdir "$fromdir/dir/subdir"
99 echo some data > "$fromdir/dir/subdir/foobar.baz"
100 mkdir "$fromdir/dir/subdir/subsubdir"
102 ls -ltr /etc > "$fromdir/dir/subdir/subsubdir/etc-ltr-list"
104 ls -ltr / > "$fromdir/dir/subdir/subsubdir/etc-ltr-list"
106 mkdir "$fromdir/dir/subdir/subsubdir2"
108 ls -lt /bin > "$fromdir/dir/subdir/subsubdir2/bin-lt-list"
110 ls -lt / > "$fromdir/dir/subdir/subsubdir2/bin-lt-list"
114 # ls -lR "$srcdir" | head -10 || echo failed
119 # Many machines do not have "mkdir -p", so we have to build up long paths.
126 if echo $p | grep '^/' >/dev/null
131 # This will break if $1 contains a space.
132 for c in `echo $p | tr '/' ' '`
134 if [ -d "$c" ] || mkdir "$c"
138 echo "failed to create $c" >&2; return $?
146 ###########################
147 # Run a test (in '$1') then compare directories $2 and $3 to see if
148 # there are any difference. If there are, explain them.
150 # So normally basically $1 should be an rsync command, and $2 and $3
151 # the source and destination directories. This is only good when you
152 # expect to transfer the whole directory exactly as is. If some files
153 # should be excluded, you might need to use something else.
158 # We can just write everything to stdout/stderr, because the
159 # wrapper hides it unless there is a problem.
161 echo "Running: \"$1\""
164 if [ $status != 0 ]; then
169 echo "check how the files compare with diff:"
171 for f in `cd "$2"; find . -type f -print `
173 diff $diffopt "$2"/"$f" "$3"/"$f" || failed=YES
177 echo "check how the directory listings compare with diff:"
179 ( cd "$2" && rsync_ls_lR . ) > "$tmpdir/ls-from"
180 ( cd "$3" && rsync_ls_lR . ) > "$tmpdir/ls-to"
181 diff $diffopt "$tmpdir/ls-from" "$tmpdir/ls-to" || failed=YES
182 if [ -z "$failed" ] ; then
190 build_rsyncd_conf() {
191 # Build an appropriate configuration file
192 conf="$scratchdir/test-rsyncd.conf"
193 echo "building configuration $conf"
196 pidfile="$scratchdir/rsyncd.pid"
197 logfile="$scratchdir/rsyncd.log"
200 # rsyncd configuration file autogenerated by $0
204 hosts allow = localhost, 127.0.0.1
225 date >"$fromdir/referent"
226 ln -s referent "$fromdir/relative"
227 ln -s "$fromdir/referent" "$fromdir/absolute"
228 ln -s nonexistent "$fromdir/dangling"
229 ln -s "$srcdir/rsync.c" "$fromdir/unsafe"
239 echo "$@" > "$tmpdir/whyskipped"
243 # It failed, but we expected that. don't dump out error logs,
244 # because most users won't want to see them. But do leave
245 # the working directory around.
251 # Determine what shell command will appropriately test for links.
252 ln -s foo "$scratchdir/testlink"
253 for cmd in test /bin/test /usr/bin/test /usr/ucb/bin/test /usr/ucb/test
257 if $cmd $switch "$scratchdir/testlink" 2>/dev/null
260 TEST_SYMLINK_CMD="$cmd $switch"
261 # i wonder if break 2 is portable?
266 # ok, now get rid of it
267 rm "$scratchdir/testlink"
270 if [ "x$TEST_SYMLINK_CMD" = 'x' ]
272 test_fail "Couldn't determine how to test for symlinks"
274 echo "Testing for symlinks using '$TEST_SYMLINK_CMD'"
278 # Test whether something is a link, allowing for shell peculiarities
280 # note the variable contains the first option and therefore is not quoted
281 $TEST_SYMLINK_CMD "$1"
285 # We need to set the umask to be reproducible. Note also that when we
286 # do some daemon tests as root, we will setuid() and therefore the
287 # directory has to be writable by the nobody user in some cases. The
288 # best thing is probably to explicitly chmod those directories after