No it was not. Why don't you just create the directory?
In the end that's what I had to do with PuTTYs plink.exe and `mkdir -p`, but the reason for it in my case was the remote machine is expected to be re-created at any time, making the remote directory something that could exist, or could not. So having an automated script fail because it tried to make a directory that already existed was a pain. See the following:
Error creating folder '/opt/app/web'.
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Common reasons for the Error code 4 are:
- Renaming a file to a name of already existing file.
- Creating a directory that already exists.
- Moving a remote file to a different filesystem (HDD).
- Uploading a file to a full filesystem (HDD).
- Exceeding a user disk quota.
(A)bort, (R)etry, (S)kip: Skip
I think the docs say there's a way to ignore this and continue on but I wasn't able to get it to work.
Thank you for the reply, though. You can consider my specific problem solved via workaround; but I would have liked to avoid using plink.exe for this.