rsync - Sep 2008 - DO NOT REPLY [Bug 5792] New: rsync fails to log files "sent" with options: --itemize-changes -n --log-file

https://bugzilla.samba.org/show_bug.cgi?id=5792

           Summary: rsync fails to log files "sent" with options:
--itemize-
                    changes -n --log-file
           Product: rsync
           Version: 3.0.2
          Platform: PPC
        OS/Version: Mac OS X
            Status: NEW
          Severity: minor
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: denis.laplante@ubc.ca
         QAContact: rsync-qa@samba.org


I find a discrepancy between screen output and log file output when running
rsync (version 3.0.2 via macports on MacOsX-10.4 PPC) in dry-run mode.
I find no discrepancy when I omit the "-n" option.  The screen listing
seems
correct with/without "-n", as well as files copied.

/opt/local/bin/rsync -n -i --stats -aES -x --exclude-from ${EXCL_FILE}
--log-file=${LOG_FILE} / /Volumes/${BACKUP_DISK}

Missing from the LOG_FILE copy are all the files that would have been sent
(prefixed with ">").
Below are 6 consecutive lines from screen output of above command - only the
last line appears in ${LOG_FILE}:
>f+++++++++ .hotfiles.btree
>f..t...... .Spotlight-V100/.journalHistoryLog
>f..t...... .Spotlight-V100/.store.db
>f..t...... .Spotlight-V100/ContentIndex.db
>f..t...... .Spotlight-V100/store.db
.d..t...... Library/Caches/

This combination of options is important to me while debugging a script to
backup my system.  I next plan to use the MacOsX "bless" command on
the backup
filesystem to make it bootable.  Note that the latest MacOsX-10.5 supplies
version 2.6.9 (2006) of rsync, which is unsuitable for Mac "resource
forks" in
incremental mode and lacks bug fixes and useful features.

VERSION: /opt/local/bin/rsync --version
rsync  version 3.0.2  protocol version 30
Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, no symtimes

Not tested on any other hardware or software.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=5792





------- Comment #1 from matt@mattmccutchen.net  2008-09-24 15:20 CST -------
I can reproduce the described behavior with the latest development rsync on
Linux: in dry-run mode, the log file seems to contain all itemize entries
except for regular file transfers (first character >).  With rsync 2.6.9, the
log contains no itemize entries at all.

What is the expected behavior here?  I know that the client's stdout is
supposed to be the same as on a real run and a daemon's log is supposed to
record only what actually happened (i.e., nothing on a dry run), but I'm not
familiar with the expected behavior for a client log file.  That should
probably be documented in the man page description of --log-file.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=5792


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Comment #2 from wayned@samba.org  2008-10-02 14:07 CST -------
The current code logs the same way for a --log-file as it does for a daemon
log, which means that it does not log transfers that aren't really
transfers.
You can instead use --out-format to change what rsync outputs, and the output
will be consistent in dry-run mode with the normal-mode output.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=5792


matt@mattmccutchen.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Comment #3 from matt@mattmccutchen.net  2008-10-02 20:07 CST -------
What is the justification for a client log file containing all itemize lines
*except* regular file transfers?  If it is to be consistent with a daemon, I
would expect to see no itemize lines at all on a dry run.

Whatever the expected behavior is, it should be documented in the man page. 
The man page does say that --log-file is "similar to the logging that a
daemon
does".  Thus, it might suffice to state in the description of
"transfer
logging" in rsyncd.conf(5) that nothing is logged on a dry run.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=5792


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|wayned@samba.org            |matt@mattmccutchen.net
             Status|REOPENED                    |NEW




------- Comment #4 from wayned@samba.org  2008-10-03 00:36 CST -------

https://bugzilla.samba.org/show_bug.cgi?id=5792

Stéphane Gourichon <stephane_sambabugz at gourichon.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stephane_sambabugz at gouricho
                   |                            |n.org

--- Comment #5 from Stéphane Gourichon <stephane_sambabugz at
gourichon.org> ---
Created attachment 14454
  --> https://bugzilla.samba.org/attachment.cgi?id=14454&action=edit
Fix bug 5792 by documenting existing behavior.

Fix bug 5792 by documenting existing behavior.

This fulfills a wish by bug assignee Matt McCutchen
https://bugzilla.samba.org/show_bug.cgi?id=5792

-- 
You are receiving this mail because:
You are the QA Contact for the bug.