On Thu, Feb 26, 2004 at 08:05:30AM -0600, Trey Nolen wrote:
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
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
That lack of deletion is fixed in 2.6.0. You can work around the
problem by either getting rid of the -R option (you don't need it in
that particular command) or by specifying /. instead of / as the
source of your copy.
That did the trick! Thanks!
Trey Nolen
--
To unsubscribe or
On Wed, Feb 25, 2004 at 08:36:26PM -0600, Trey Nolen wrote:
rsync -avR -e ssh --numeric-ids --delete --progress --delete-after
--ignore-errors --exclude /proc/ / [EMAIL PROTECTED]:/
That lack of deletion is fixed in 2.6.0. You can work around the
problem by either getting rid of the -R option
On Wed, Feb 25, 2004 at 08:36:26PM -0600, Trey Nolen wrote:
I've got an issue with remote files being deleted after the local file has
been deleted. For some reason, this isn't happening. I'm running rsync
2.5.6 protocol 26 (yes, I know there are newer versions, but logistics
dictates that I
