August 10, 201213 yr I've been looking at the logging the mover generates: Aug 10 01:00:01 Tower logger: mover started Aug 10 01:00:01 Tower logger: skipping Apps/ Aug 10 01:00:01 Tower logger: skipping Downloads/ Aug 10 01:00:01 Tower logger: moving TV Series/ Aug 10 01:00:01 Tower logger: ./TV Series/Breaking Bad/Season 5/Breaking Bad.S05E02.Madrigal.720p.DD5.1.WEB-DL.H.264.mkv Aug 10 01:00:01 Tower logger: .d..t...... ./ Aug 10 01:00:01 Tower logger: .d..t...... TV Series/ Aug 10 01:00:01 Tower logger: .d..t...... TV Series/Breaking Bad/ Aug 10 01:00:01 Tower logger: .d..t...... TV Series/Breaking Bad/Season 5/ Aug 10 01:00:01 Tower logger: >f+++++++++ TV Series/Breaking Bad/Season 5/Breaking Bad.S05E02.Madrigal.720p.DD5.1.WEB-DL.H.264.mkv Aug 10 01:00:01 Tower logger: mover finished But what does 'd..t......' mean? Why aren't the locations logged where things are actually moved to? That's the whole purpose of logging i would say. And what does 'f+++++++++++' stand for?
August 10, 201213 yr http://www.andreafrancia.it/2010/03/understanding-the-output-of-rsync-itemize-changes.html
August 10, 201213 yr Author I did not know the mover was based upon or implemented as rsync. That explains a lot.
Archived
This topic is now archived and is closed to further replies.