开云体育

I’m not entirely clear what you’re asking. Please can you clarify. Also attach a sample IBC logfile so I can see what settings you’re using. IBC works exactly the same on Linux as on Windows.

Thanks Richard for your reply! I couldnt find the log file anymore since I re-ran the bat and it overwrote it. Using IBC 3.16 and TWS 10.21. I actually did change it from 40-100seconds as stated in

Thanks Richard for this awesome tool. I've been using latest version for more last few weeks now but i couldn't see any automated restart of TWS session after scheduled restart in TWS every day.?

Ok, this is just a result of TWS taking a long time to display the main form after a 2FA login. The way to avoid this is to set SecondFactorAuthenticationExitInterval in config.ini to a larger value.

I experienced the same issue last night. I’ll try to investigate this later today. By the way, for future reference, it’s always helpful to give as much information as possible. For example, you

Ive manually checked and realised even after logging in successfully with 2FA mobile, the app/tws closes after 40 seconds. I've also set the timeout to be 100s and still no differences, kills both at

Fair enough, thanks!

Just create a socket connection, send the command, read the response, close the connection. I’m not a Pythonista, but I imagine this will be pretty straightforward. Sent: 01 February 2023 22:31 To:

Just saw this, thanks. Need to figure out how to send telnet commands from python now…

Thank you Richard.? I modified the scheduled task from Start TWS Live (daily) to Start TWS Live (weekly) starting Sunday and running for 6 days, checking if it runs every 10 minutes

The screenshot shows that the first task is being stopped at 03:36:57 because it reaches its timeout. That means that when the next schedule start arrives at 03:42:01, it is no longer running, so a

As seen in the attached scheduled task history, it's the culprit..? I guess I need to disable it and enable it at exactly 2:32am, my first trigger time? Again, as per today's C:\Jts\launcher.log it

If you started it at 03:42 on Sunday, then I think it will assume that it was a start in the week that ENDS on that Sunday. So when it gets to the configured auto-restart time it thinks it hasn’t

3) See attached?C:\Jts\launcher.log ( as opposed to C:\Jts\1019\launcher.log which is not written to when using IBC ) There was a Monday 2:30am restart as expected, with no 2FA. But then again at

I'm using IBC 3.16 and TWS 10.19 with "Auto restart" enabled at 2:30am.? The first run of IBC+TWS was Sunday at 3:42am, but on Monday at 3:42 I'm asked for 2FA.? The expected behavior is no 2FA for

Oops, sorry, forgot to reply… The restart script is Windows-only (though the target TWS/Gateway can be anywhere). I don’t bother providing a script for Linux because it’s easy to script telnet

Hi Richard, I may have jumped the gun on this :). Is the restart script only available for windows in this version or am I being thick again?

No. The auto-restart facilities in IBC are built on those in TWS/Gateway, introduced back in version 974 (if I remember correctly) and much improved in recent versions. These mechanisms depend on

Does it mean that if the IBC is not working or closed by any accident, it would automatically restart itself? 「Richard L King <rlking@...>」在 2023年1月21日 週六，上午2:58 寫道：

The restart command works (on Ubuntu) for me and skips the 2FA! This is great for the occasionally needed mid-week restart. Thanks again, Richard.