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
39 echo $ECHO_N "Test $1: $ECHO_C"
45 echo "$ECHO_T failed!"
56 find "$@" -print | sort | sed 's/ /\\ /g' | xargs "$TOOLDIR/tls"
65 # Build test directories $todir and $fromdir, with $fromdir full of files.
68 # Clean before creation
72 [ -d "$tmpdir" ] || mkdir "$tmpdir"
73 [ -d "$fromdir" ] || mkdir "$fromdir"
74 [ -d "$todir" ] || mkdir "$todir"
76 # On some BSD systems, the umask affects the mode of created
77 # symlinks, even though the mode apparently has no effect on how
78 # the links behave in the future, and it cannot be changed using
79 # chmod! rsync always sets its umask to 000 so that it can
80 # accurately recreate permissions, but this script is probably run
81 # with a different umask.
83 # This causes a little problem that "ls -l" of the two will not be
84 # the same. So, we need to set our umask before doing any creations.
87 touch "$fromdir/empty"
88 mkdir "$fromdir/emptydir"
90 # a hundred lines of text or so
91 rsync_ls_lR "$srcdir" > "$fromdir/filelist"
93 echo $ECHO_N "This file has no trailing lf$ECHO_C" > "$fromdir/nolf"
95 ln -s nolf "$fromdir/nolf-symlink"
98 cat "$srcdir"/*.c > "$fromdir/text"
100 cp "$fromdir/text" "$fromdir/dir"
101 mkdir "$fromdir/dir/subdir"
102 echo some data > "$fromdir/dir/subdir/foobar.baz"
103 mkdir "$fromdir/dir/subdir/subsubdir"
105 ls -ltr /etc > "$fromdir/dir/subdir/subsubdir/etc-ltr-list"
107 ls -ltr / > "$fromdir/dir/subdir/subsubdir/etc-ltr-list"
109 mkdir "$fromdir/dir/subdir/subsubdir2"
111 ls -lt /bin > "$fromdir/dir/subdir/subsubdir2/bin-lt-list"
113 ls -lt / > "$fromdir/dir/subdir/subsubdir2/bin-lt-list"
117 # ls -lR "$srcdir" | head -10 || echo failed
122 # Many machines do not have "mkdir -p", so we have to build up long paths.
129 if echo $p | grep '^/' >/dev/null
134 # This will break if $1 contains a space.
135 for c in `echo $p | tr '/' ' '`
137 if [ -d "$c" ] || mkdir "$c"
141 echo "failed to create $c" >&2; return $?
149 ###########################
150 # Run a test (in '$1') then compare directories $2 and $3 to see if
151 # there are any difference. If there are, explain them.
153 # So normally basically $1 should be an rsync command, and $2 and $3
154 # the source and destination directories. This is only good when you
155 # expect to transfer the whole directory exactly as is. If some files
156 # should be excluded, you might need to use something else.
161 # We can just write everything to stdout/stderr, because the
162 # wrapper hides it unless there is a problem.
164 echo "Running: \"$1\""
167 if [ $status != 0 ]; then
172 echo "check how the directory listings compare with diff:"
174 ( cd "$2" && rsync_ls_lR . ) > "$tmpdir/ls-from"
175 ( cd "$3" && rsync_ls_lR . ) > "$tmpdir/ls-to"
176 diff $diffopt "$tmpdir/ls-from" "$tmpdir/ls-to" || failed=YES
179 echo "check how the files compare with diff:"
181 if [ "x$4" != x ]; then
182 echo " === Skipping (as directed) ==="
184 diff -r $diffopt "$2" "$3" || failed=YES
188 if [ -z "$failed" ] ; then
196 build_rsyncd_conf() {
197 # Build an appropriate configuration file
198 conf="$scratchdir/test-rsyncd.conf"
199 echo "building configuration $conf"
202 pidfile="$scratchdir/rsyncd.pid"
203 logfile="$scratchdir/rsyncd.log"
206 # rsyncd configuration file autogenerated by $0
210 hosts allow = localhost, 127.0.0.1
231 date >"$fromdir/referent"
232 ln -s referent "$fromdir/relative"
233 ln -s "$fromdir/referent" "$fromdir/absolute"
234 ln -s nonexistent "$fromdir/dangling"
235 ln -s "$srcdir/rsync.c" "$fromdir/unsafe"
245 echo "$@" > "$tmpdir/whyskipped"
249 # It failed, but we expected that. don't dump out error logs,
250 # because most users won't want to see them. But do leave
251 # the working directory around.
257 # Determine what shell command will appropriately test for links.
258 ln -s foo "$scratchdir/testlink"
259 for cmd in test /bin/test /usr/bin/test /usr/ucb/bin/test /usr/ucb/test
263 if $cmd $switch "$scratchdir/testlink" 2>/dev/null
266 TEST_SYMLINK_CMD="$cmd $switch"
267 # i wonder if break 2 is portable?
272 # ok, now get rid of it
273 rm "$scratchdir/testlink"
276 if [ "x$TEST_SYMLINK_CMD" = 'x' ]
278 test_fail "Couldn't determine how to test for symlinks"
280 echo "Testing for symlinks using '$TEST_SYMLINK_CMD'"
284 # Test whether something is a link, allowing for shell peculiarities
286 # note the variable contains the first option and therefore is not quoted
287 $TEST_SYMLINK_CMD "$1"
291 # We need to set the umask to be reproducible. Note also that when we
292 # do some daemon tests as root, we will setuid() and therefore the
293 # directory has to be writable by the nobody user in some cases. The
294 # best thing is probably to explicitly chmod those directories after