Bug first seen on 3.6.3, also validated on 4.1.6 Escaping the semi-colon doesn't work either. What I've tried: smbclient //server/share -c 'cd "/path;with;semi-colon"; put "file" "file"' smbclient //server/share -c 'put "file;with;semi-colon" "file"' smbclient //server/share -c 'cd "/path\;with\;semi-colon"; put "file" "file"' smbclient //server/share -c 'put "file\;with\;semi-colon" "file"' smbclient //server/share -c 'cd "/path\\;with\\;semi-colon"; put "file" "file"' smbclient //server/share -c 'put "file\\;with\\;semi-colon" "file"' Proposed solution: parse "\;" as literal ";"
Hi All, I have just hit the same issue... Any update on this? Kind regards, Pieter
(In reply to Bernard Kerckenaere from comment #0) How you created path or file with semicolon? # touch file1;_5 -bash: _5: command not found # Can you please provide exact filename,directory names and smbclient command run with them.
> touch "file1;_5"