to git to make the SMB pipe non-blocking, which is the same change I made to Tar.pm in 4.1.3 to fix a stall issue with tar reported by Matt Bedynek.
Here's a diff that you could apply with patch:
https://github.com/backuppc/backuppc/commit/b0ae4bca583b7882ce1c51f20391b681440a63c6.diff.
This might fix Dan's instance of the problem.
However, the log file that Tim sent shows that something else is going wrong with his setup - smbclient is still running (doing something), but BackupPC_tarExtract sees no further output. Could Micheal's theory be correct - smbclient is repeatedly trying to read a dll? Unfortunately, I'm not familiar with windows or SMB.
Tim - you could test standalone (without BackupPC involved) by running something like:
/usr/bin/smbclient '\\pelican\C$' -U backup -E -d 1 -c tarmode full -Tc – | tar tvf -
and waiting until either it completes, or it is stalled with no output from tar. You could then re-run with higher debug levels on smbclient (increase the "-d 1" to "-d 3" or so).
Craig