smbclient \\\\client1\\C\$ -I 192.168.1.1 -U backuppc -E -N -d 1 -c tarmode\ full -Tc -
it appears as though BackupPC loads the user password into the PASSWD environment variable to login without password prompts. When I switch smbclient from 2.2.8a to 3.0.0beta2, I get the following error message in the BackupPC logs:
===========================
Error opening local file \\client1\C$ - Permission denied
Usage: [-?EVNk] [--usage] [-R NAME-RESOLVE-ORDER] [-M HOST] [-I IP] [-L HOST]
[-t CODE] [-m LEVEL] [-T <c|x>IXFqgbNan] [-D DIR] [-c ARG] [-b BYTES]
[-p PORT] [-d DEBUGLEVEL] [-s CONFIGFILE] [-l LOGFILEBASE]
[-O SOCKETOPTIONS] [-n NETBIOSNAME] [-W WORKGROUP] [-i SCOPE]
[-U USERNAME] [-A FILE] service <password>
===========================
The man page for smbclient 3.0.0beta2 appears to be unchanged from the 2.x releases, so I'm a little at a loss as to what to do. I tried rearranging the arguments a little:
=========================== smbclient -I 192.168.1.1 -U backuppc -E -N -d 1 \\\\client1\\C\$
gets me connected to the Windows system and left at the "smb: \>" prompt ===========================
===========================
smbclient -I 192.168.1.1 -U backuppc -E -N -d 1 -c tarmode\ full \\\\client1\\C\$
spits out "tarmode is now full, system, hidden, noreset, verbose" and then exits
===========================
===========================
smbclient -I 192.168.1.1 -U backuppc -E -N -d 1 -c tarmode\ inc -Tc - \\\\client1\\C\$
spits out: tarmode is now full, system, hidden, noreset, verbose NT_STATUS_NO_SUCH_FILE listing \192.168.1.1 NT_STATUS_NO_SUCH_FILE listing \-U NT_STATUS_NO_SUCH_FILE listing \backuppc NT_STATUS_NO_SUCH_FILE listing \-E NT_STATUS_NO_SUCH_FILE listing \-N NT_STATUS_NO_SUCH_FILE listing \-d NT_STATUS_NO_SUCH_FILE listing \1 NT_STATUS_NO_SUCH_FILE listing \-c NT_STATUS_NO_SUCH_FILE listing \tarmode inc NT_STATUS_NO_SUCH_FILE listing \-Tc NT_STATUS_OBJECT_NAME_NOT_FOUND listing \client1\C$ tar: dumped 0 files and directories Total bytes written: 0 ===========================
It appears as though smbclient has broken argument parsing, as well as having an out of date man page. Any ideas on what I should try?
Steve
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba