Hi,
I think there is a classic use of mkdir instead of mkdir -p type problem
in rsync, ie where a new directory of depth greater than one needs to be
created. Has this been solved? Or is it some other issue? Or is it
the responsibility of the user? :-P
I might take a look at it later -- I suspect it is trivial to fix.
Cheers James
===== Examples =====
This doesn't work:
root@fox:/backup/mirror > rsync --verbose --archive --stats --compress
--owner --delete --exclude "*.o" --exclude "*.so" --exclude "core"
ape:/home/* /backup/mirror/ape/home
receiving file list ... done
mkdir /backup/mirror/ape/home : No such file or directory (1)
root@fox:/backup/mirror >
But this does (ie /backup/mirror/ape/home is /backup/mirror/ape/home)
root@fox:/backup/mirror > rsync --verbose --archive --stats --compress
--owner --delete --exclude "*.o" --exclude "*.so" --exclude "core"
ape:/home/* /backup/mirror/ape
receiving file list ... done
created directory /backup/mirror/ape
<snip>
===== rsync versions (fox is server; ape is client) ======
receiving file list ... root@fox:/var/BACKUP/rsync > rsync --version
rsync version 2.3.2 protocol version 21
Written by Andrew Tridgell and Paul Mackerras
root@fox:/var/BACKUP/rsync > rsh ape rsync --version
rsync version 2.2.1 protocol version 19
Written by Andrew Tridgell and Paul Mackerras
--
James Jones, GMRS Software GmbH,
Innsbrucker Ring 159, 81669 Muenchen
tel: (089) 680792-30, fax: (089) 680792-92
mailto:[EMAIL PROTECTED] http://www.gmrs.de
