Step between --dry-run and running?

[Tuc at T-B-O-H.NET]

> 
> On Sat, 2008-05-31 at 18:16 -0400, Tuc at T-B-O-H.NET wrote:
> > > That would be --only-write-batch.
> > =20
> > 	Hrm, so it does.... But creates a $FILE.sh filename. Any
> > way to prevent that part?
> 
> No.  If you don't want the $FILE.sh, just delete it.
>

	It needs to be able to write it first......

FreeBSD:

himinbjorg# touch /dev/null.sh
touch: /dev/null.sh: Operation not supported

	Not so good, but......

Linux:
[root at ports ~]# touch /dev/null.sh
[root at ports ~]# ls -l /dev/null.sh
-rw-r--r--  1 root root 0 Jun  1 13:13 /dev/null.sh

	Thats ok... The first system I need to
implement it on is a Linux, so I guess it won't be an
issue, but the next is a FreeBSD.. Maybe if I just do :

himinbjorg# ln -s /dev/null b
himinbjorg# ls -l b
lrwxr-xr-x  1 root  wheel  9 Jun  1 13:16 b -> /dev/null
himinbjorg# cat /boot/kernel >b
himinbjorg# ls -l b
lrwxr-xr-x  1 root  wheel  9 Jun  1 13:16 b -> /dev/null

	That way its not inside the /dev directory...
I don't know if rsync does anything special with the
file presented in --only-write-batch, but if it just
opens for write, then shouldn't be an issue.
 
> > Also, should running it twice in a row
> > quickly produce 2 files that should diff the same, or is something
> > stored in there that would prevent a diff from being the same?
> > (Timestamp, etc)
> 
> There is one thing that impedes reproducibility of batch files: rsync
> uses the current time as a seed for the delta-transfer algorithm so that
> delta-transfer corruptions won't occur repeatedly for the same file.  If
> you specify your own seed with --checksum-seed and nothing in the source
> or destination changes, then the batch files should be identical.
> 
	Ok. I wasn't looking for identical, just a reason why. Thats a
"reason why" in my book. 

	Thanks for all the help!

			Tuc