i'd found something weird. this two lines are from a windows implementation of rsync: 2005/09/22 20:05:33 [520] recv xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] NMSCORE () BACKUP/IDS_HeartlandBank_db_200509220206.BAK 4449207808 2005/09/22 20:17:40 [520] rsync: write failed on "/BACKUP/IDS_HeartlandBank_db_200509220831.BAK" (in NMSCORE): No space left on device (28) as you can see, the error below doesn't match the file name of the previous line. i've read some logs from a novell implementation of rsync and it seems to never happen that way. each error seems to point to the last file rsync tried to send. is that the way it works? that is a difference between the two implementations of rsync? -------------- next part -------------- HTML attachment scrubbed and removed
On Mon, Sep 26, 2005 at 05:27:16PM -0300, Mario Tambos wrote:> as you can see, the error below doesn't match the file name of the > previous line.Older versions of rsync always logged after the file had been completed. Newer versions of rsync log at the start of an item, if possible (i.e. as long as transmission-statistics aren't requested, such as %b or %c). Thus, the "recv" line is for an already-completed file and the "write failed" line is the file rsync is actively working on. ..wayne..