(answering to the bug report so that your own answer...and mine...are recorded there)
Quoting Krassimir Grozdanov (k.grozda...@bnra.bg): > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The bug can be reproduced with smbclient 3.6.4-1, and I think with > 3.6.3. I am not very familiar how exactly backuppc proceeds, but this is > the command it uses for backup: > > $smbClientPath \\$host\$shareName $I_option -U $userName -E -d 1 -c > tarmode\ full -Tc$X_option - $fileList > > This is the description of all variables > > $smbClientPath path of smbclient > <http://bnsa864/backuppc/index.cgi?action=view&type=docs#_conf_smbclientpath_> > $host host to backup/restore > $shareName share name > $userName user name > $fileList list of files to backup (based on exclude/include) > $I_option optional -I option to smbclient > $X_option exclude option (if $fileList is an exclude list) > > > I have tested the command manually, and it stops when trying to list > System Volume Information on the remote share with > the following errors: > > directory \System Volume Information\ > NT_STATUS_ACCESS_DENIED listing \System Volume Information\* > NT_STATUS_ACCESS_DENIED listing \\* (it stops here) > > And this is the output with smbclient 3.5.6 > > directory \System Volume Information\ > NT_STATUS_ACCESS_DENIED listing \System Volume Information\* > > After that the backup continues normally. > > > I hope this information will be helpful. OK, so the problem seems to be that smbclient now insist on listing the content of directories even when these are explicitely excluded. I guess one can see that as a regression and it's worth being reported upstream. Thanks for your input.
signature.asc
Description: Digital signature