On 7/2/21 7:01 PM, Phil Kennedy wrote:
If memory serves, the crux of the issue was that smbclient (well, samba
in general) changed the way verbose output was handled. The tar errors
(unexpected end of file) resulted from a samba not reporting the same
number of files (specifically, reporting 0 files backed up as verbose
output was broken) backed up versus the actual number of files moved.
There is a workaround to get samba going again, but I can't seem to
recreate the search terms I used to find the fix.
(Apologies if I'm confusing a separate issue with the one OP brought up.)
~Phil
You got the right issue. There is an open bug report,
https://github.com/backuppc/backuppc/issues/404
--
Tim Evans | 5 Chestnut Court
443-394-3864 | Owings Mills, MD 21117
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
