script fails with return code 0
Using WinSCP 4.3.5 (Build 1463) on Windows XP SP3. I'm using the command line version.
WinSCP can falsely detect errors in the call command when the return code is 0. If the return code 0, then there should be no error. This is demonstrated below:
This doesn't happen if I use stdout instead of stderr. So I'm guessing WinSCP is checking stderr when it should only be checking the return code.
Keep up the good work, your software is really useful! Thank you.
WinSCP can falsely detect errors in the call command when the return code is 0. If the return code 0, then there should be no error. This is demonstrated below:
winscp> option echo off echo off winscp> option bat abort batch abort winscp> option confirm off confirm off winscp> option transfer automatic transfer automatic winscp> open -timeout=1 root:FM@192.168.101.2 Searching for host... Connecting to host... Authenticating... Using username \"root\". Authenticating with pre-entered password. Authenticated. Starting the session... Reading remote directory... Session started. Active session: [1] root@192.168.101.2 winscp> call echo "asdf" >&2 Searching for host... Connecting to host... Authenticating... Using username \"root\". Authenticating with pre-entered password. Authenticated. Starting the session... Reading remote directory... Session started. asdf Command 'echo "asdf" >&2' failed with return code 0 and error message asdf.
This doesn't happen if I use stdout instead of stderr. So I'm guessing WinSCP is checking stderr when it should only be checking the return code.
Keep up the good work, your software is really useful! Thank you.
