-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set-SCPItem for a directory does not support unregular characters #535
Comments
you may try to use |
For which part? The sending of directory with unregular characters, or the handling of "no such file or directory"? (Both?) |
the single command you use in your example - |
I still have this problem and not fix it yet, and I'm trying tying to use Set-SCPItem with for loop to looping on each file on my folder and then copy it into my server.
|
What special characters are in your case causing it to fail?
|
$ComputerName = "MYSERVERIP" the connection and handshake work well but the upload start: |
If you specify a directory it will copy the directory with its name as is to the specified path. It is behaving as expected. If you want to upload each file in the directory individually then you will need a loop to upload each to the root of the target path. SFTP is a better option since you will mot have to establish a tear down a connection for each file
|
Trying to send a whole directory using Set-SCPItem that contains unregluar characters in its name leads to what seems like a locked terminal and nothing happens. I haven't investigated this deeply (maybe the same goes for regular files as well) but a command like this:
This will just hang forever (at least over night 😅) and cant be interupted with ctrl+c. I'm gussing it has to do with some path-parsing on the destination side as ( needs to be escaped 🤔 ( on a *unix machine
As a sidenote; if one tries to send a directory, and a directory with the same name doesn't exist on the Destination, one would get a
Which is a little counter-intuitive when one tries to send a complete directory, but not a huge problem. Just annoyance 😇
The text was updated successfully, but these errors were encountered: