rsync - Sep 2005 - Logging of attribute changes when no data is transferred?

How can I get rsync to write a log record (like --log-format does for data
transfer) when no content needs to be transferred but attributes (owner, group,
mode, ...) are changed?

-- 
Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/                   | http://Mielke.cc/bible/

On Wed, Sep 14, 2005 at 06:53:46PM -0400, Dave Mielke
wrote:
> How can I get rsync to write a log record (like --log-format does for
> data transfer) when no content needs to be transferred but attributes
> (owner, group, mode, ...) are changed?
Use -i or put %i into your --log-format.  See the 2.6.6 manpage for details.

..wayne..

Using rsync-2.6.6, I''m getting:

   unable to alloc 417794083 bytes

Under what circumstances would rsync allocate a block that large? Must it be
able to allocate a block as large as the largest file or something? Is there a
way to limit it?

-- 
Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2A 1H7   | if you''re concerned about
Hell.
http://FamilyRadio.com/                   | http://Mielke.cc/bible/

On Wed, 21 Dec 2005, Dave Mielke <dave@mielke.cc>
wrote:
> Using rsync-2.6.6, I''m getting:
> 
>    unable to alloc 417794083 bytes
> 
> Under what circumstances would rsync allocate a block that large? Must it
be
> able to allocate a block as large as the largest file or something? Is
there a
> way to limit it?
Rsync uses buffered I/O for file transfer - it does not allocate memory
based on the size of a file.

The size is not an even number, so it''s not from an flist expansion or
any other buffer allocation.

Hmm.  That''s not even a message from rsync.  Rsync reports:

  ERROR: out of memory in FOO

where FOO is a tag indicating where the problem happened (for example,
the name of the subroutine).

You need to provide more info - O/S, command used, what had happened
up to the error, etc.  Use -vv with rsync to get more info.

    John