[Bug 1258219] Re: smbclient 'put' fails with absolute path to local file

Macarro 1258219 at bugs.launchpad.net
Fri May 22 20:21:07 UTC 2015


I know this thread is quite old, but just in case...

Sorry, Robie, but I don't understand you. What could be the advantage or
intentionality behind it? I mean, smbclient is a linux program and the
put command is to copy a local file (so, from linux path) to a remote
computer. Why should you need to consider any kind of path manipulation?

Regards

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1258219

Title:
  smbclient 'put' fails with absolute path to local file

Status in samba package in Ubuntu:
  New

Bug description:
  smbclient 2:3.6.3-2ubuntu2.6 on Ubuntu 12.04.3 LTS

  When issuing command similar to
  "smbclient --user=DOMAIN/domainuser -c "put /path/to/file.zip" //Machine/Share machinePassword

  rather than upload the local file /path/to/file.zip to remote //Machine/Share as expected, smbclient complains with the error
  "NT_STATUS_OBJECT_NAME_INVALID opening remote file \/path/to/file.zip"

  
  At the moment, for a workaround, we are using -c "lcd /path/to; put file.zip" which has been working, but this only works because the very simple script knows the absolute paths for the files we are backing up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1258219/+subscriptions



More information about the foundations-bugs mailing list