# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-TMP="$scratchdir"
-FROM=${TMP}/from
-TO=${TMP}/to
-LOG=${TMP}/log
-RSYNC="$rsync_bin"
+tmpdir="$scratchdir"
+fromdir=$tmpdir/from
+todir=$tmpdir/to
+chkdir=$tmpdir/chk
+
+# Berkley's nice.
+PATH="$PATH:/usr/ucb"
+
+if diff -u $srcdir/testsuite/rsync.fns $srcdir/testsuite/rsync.fns >/dev/null 2>&1; then
+ diffopt="-u"
+else
+ diffopt="-c"
+fi
runtest() {
echo $ECHO_N "Test $1: $ECHO_C"
if eval "$2"
then
- echo "${ECHO_T} done."
+ echo "$ECHO_T done."
return 0
else
- echo "${ECHO_T} failed!"
+ echo "$ECHO_T failed!"
return 1
fi
}
rsync_ls_lR() {
- find "$@" -print | sort | xargs $TLS
+ find "$@" -print | sort | xargs "$TOOLDIR/tls"
+}
+
+rsync_getgroups() {
+ "$TOOLDIR/getgroups"
}
####################
-# Build test directories TO and FROM, with FROM full of files.
+# Build test directories $todir and $fromdir, with $fromdir full of files.
hands_setup() {
# Clean before creation
- rm -rf $FROM
- rm -rf $TO
+ rm -rf "$fromdir"
+ rm -rf "$todir"
- [ -d $TMP ] || mkdir $TMP
- [ -d $FROM ] || mkdir $FROM
- [ -d $TO ] || mkdir $TO
+ [ -d $tmpdir ] || mkdir "$tmpdir"
+ [ -d $fromdir ] || mkdir "$fromdir"
+ [ -d $todir ] || mkdir "$todir"
# On some BSD systems, the umask affects the mode of created
# symlinks, even though the mode apparently has no effect on how
# the same. So, we need to set our umask before doing any creations.
# set up test data
- touch ${FROM}/empty
- mkdir ${FROM}/emptydir
+ touch "$fromdir/empty"
+ mkdir "$fromdir/emptydir"
# a hundred lines of text or so
- rsync_ls_lR "${srcdir}" > ${FROM}/filelist
+ rsync_ls_lR "$srcdir" > "$fromdir/filelist"
- # This might fail on systems that don't have -n
- echo $ECHO_N "This file has no trailing lf$ECHO_C" > ${FROM}/nolf
+ echo $ECHO_N "This file has no trailing lf$ECHO_C" > "$fromdir/nolf"
umask 0
- ln -s nolf ${FROM}/nolf-symlink
+ ln -s nolf "$fromdir/nolf-symlink"
umask 022
- cat $srcdir/*.c > ${FROM}/text
- mkdir ${FROM}/dir
- cp ${FROM}/text ${FROM}/dir
- mkdir ${FROM}/dir/subdir
- mkdir ${FROM}/dir/subdir/subsubdir
- ls -ltr /etc > ${FROM}/dir/subdir/subsubdir/etc-ltr-list
- mkdir ${FROM}/dir/subdir/subsubdir2
- ls -lt /bin > ${FROM}/dir/subdir/subsubdir2/bin-lt-list
+ cat $srcdir/*.c > "$fromdir/text"
+ mkdir "$fromdir/dir"
+ cp "$fromdir/text" "$fromdir/dir"
+ mkdir "$fromdir/dir/subdir"
+ echo some data > "$fromdir/dir/subdir/foobar.baz"
+ mkdir "$fromdir/dir/subdir/subsubdir"
+ ls -ltr /etc > "$fromdir/dir/subdir/subsubdir/etc-ltr-list"
+ mkdir "$fromdir/dir/subdir/subsubdir2"
+ ls -lt /bin > "$fromdir/dir/subdir/subsubdir2/bin-lt-list"
# echo testing head:
-# ls -lR ${srcdir} | head -10 || echo failed
+# ls -lR "$srcdir" | head -10 || echo failed
}
-hands_cleanup() {
- rm -r "$TMP"
-}
-
-
-
-
####################
# Many machines do not have "mkdir -p", so we have to build up long paths.
# How boring.
# Run a test (in '$1') then compare directories $2 and $3 to see if
# there are any difference. If there are, explain them.
+# So normally basically $1 should be an rsync command, and $2 and $3
+# the source and destination directories. This is only good when you
+# expect to transfer the whole directory exactly as is. If some files
+# should be excluded, you might need to use something else.
+
checkit() {
failed=
echo ""
for f in `cd "$2"; find . -type f -print `
do
- diff -u "$2"/"$f" "$3"/"$f" || failed=YES
+ diff $diffopt "$2"/"$f" "$3"/"$f" || failed=YES
done
echo "-------------"
echo "check how the directory listings compare with diff:"
echo ""
- ( cd "$2" && rsync_ls_lR . ) > ${TMP}/ls-from
- ( cd "$3" && rsync_ls_lR . ) > ${TMP}/ls-to
- diff -c ${TMP}/ls-from ${TMP}/ls-to || failed=YES
- if [ -z "${failed}" ] ; then
+ ( cd "$2" && rsync_ls_lR . ) > "$tmpdir/ls-from"
+ ( cd "$3" && rsync_ls_lR . ) > "$tmpdir/ls-to"
+ diff $diffopt "$tmpdir/ls-from" "$tmpdir/ls-to" || failed=YES
+ if [ -z "$failed" ] ; then
return 0
else
return 1
}
-# In fact, we need a more general feature of capturing all stderr/log files,
-# and dumping them if something goes wrong.
-
-checkforlogs() {
- # skip it if we're under debian-test
- if test -n "${Debian}" ; then return 0 ; fi
-
- if [ -f $1 -a -s $1 ] ; then
- echo "Failures have occurred. $1 follows:" >&2
- cat $1 >&2
- exit 1
- fi
-}
-
-
build_rsyncd_conf() {
# Build an appropriate configuration file
conf="$scratchdir/test-rsyncd.conf"
pidfile="$scratchdir/rsyncd.pid"
logfile="$scratchdir/rsyncd.log"
- cat >$conf <<EOF
+ cat >"$conf" <<EOF
# rsyncd configuration file autogenerated by $0
pid file = $pidfile
use chroot = no
hosts allow = localhost, 127.0.0.1
log file = $logfile
+exclude = foobar.baz
+max verbosity = 9
+
+uid = 0
+gid = 0
-[test-from] = $scratchdir/daemon-from/
+[test-from]
+ path = $fromdir
read only = yes
-[test-to] = $scratchdir/daemon-to/
+[test-to]
+ path = $todir
read only = no
EOF
}
build_symlinks() {
- fromdir="$scratchdir/from"
- todir="$scratchdir/to"
mkdir "$fromdir"
date >"$fromdir/referent"
ln -s referent "$fromdir/relative"
test_skipped() {
echo "$@" >&2
+ echo "$@" > "$tmpdir/whyskipped"
exit 77
}
exit 78
}
-# be reproducible
-umask 077
\ No newline at end of file
+# Determine what shell command will appropriately test for links.
+ln -s foo "$scratchdir/testlink"
+for cmd in test /bin/test /usr/bin/test /usr/ucb/bin/test /usr/ucb/test
+do
+ for switch in -h -L
+ do
+ if $cmd $switch "$scratchdir/testlink" 2>/dev/null
+ then
+ # how nice
+ TEST_SYMLINK_CMD="$cmd $switch"
+ # i wonder if break 2 is portable?
+ break 2
+ fi
+ done
+done
+# ok, now get rid of it
+rm "$scratchdir/testlink"
+
+
+if [ "x$TEST_SYMLINK_CMD" = 'x' ]
+then
+ test_fail "Couldn't determine how to test for symlinks"
+else
+ echo "Testing for symlinks using '$TEST_SYMLINK_CMD'"
+fi
+
+
+# Test whether something is a link, allowing for shell peculiarities
+is_a_link() {
+ # note the variable contains the first option and therefore is not quoted
+ $TEST_SYMLINK_CMD "$1"
+}
+
+
+# We need to set the umask to be reproducible. Note also that when we
+# do some daemon tests as root, we will setuid() and therefore the
+# directory has to be writable by the nobody user in some cases. The
+# best thing is probably to explicitly chmod those directories after
+# creation.
+
+umask 022