cmd - WinSCP script will not exit after error, even with "option batch abort" -


For any reason, my network will not stop when my script is closed.

Here is the command:

  "% ~ dp0 \ winscp.exe" / console /script="script.txt "exit  
< P> and script.txt:

  Option Batch Abort Option open ftp: // Confirm User: pass@ftp.site.com/ cd / directory / local exit  Synchronize 

When I pull my network cable (to test for network drops), I get:

  The requested name is valid, but the requested type No data found. connection failed. (A) BORT, (R) ENCNETT (5S): .. (A) BOURT, (R) ENCNETT (0S): RECONNECT  

Try it indefinitely And will continue to connect again.

Why does the script not automatically abort? I am using the option batch mutation . Am I missing something?

This error is recoverable, so WinSCP tries to resume with the transfer Option batch abort as:

...
When the batch mode is set to on , then an option prompt is automatically Is responded negatively until a second default response of the prompt (such as the answer to a "reconnect" default to a re-connect) occurs, then the location In the case, the default answer is used (after a short time interval). See also a reconnecttime option below.
value abort as is turned on . ...

As mentioned above, you can configure how long WinSCP attempts to reconnect by using option reconnect time By default WinSCP attempts to reconnect to on / abort mode for 2 minutes again.

Note that WinSCP was essentially used to reconnect to the older versions, by default. You have to use some older versions.


Comments

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -