remote files not being deleted

[Trey Nolen]

>
> It may be that you are running out of memory.  --delete
> causes the a second file list (about 100bytes/file) to be
> created contianing all the files existing on the receiver.
> Combined with --delete-after this happens at the time when
> the memory usage is at its greatest due to copy-on-write and
> fragmentation.


Although it looks like my problem was caused by a path problem with 2.5.6
(I need to specify /. instead of / for the source), I'm interested in this
memory issue.  Is this file list created on the client side or the server
side?

Trey Nolen