If one attempts to start either the proxy or vpn client, I think there is no timeout on that operation and the visor will try to start it forever, even on continuous failed attempts to make a transport.
Instead of having to control the process via external means (i.e. running skywire-cli via timeout on linux) we should simply provide a flag so that users can specify a timeout interval.
This is mostly a consideration for testing or advanced users. For our purposes, the timeout interval specified via flag should be an integer representing time in seconds.
If one attempts to start either the proxy or vpn client, I think there is no timeout on that operation and the visor will try to start it forever, even on continuous failed attempts to make a transport.
Instead of having to control the process via external means (i.e. running
skywire-cliviatimeouton linux) we should simply provide a flag so that users can specify a timeout interval.This is mostly a consideration for testing or advanced users. For our purposes, the timeout interval specified via flag should be an integer representing time in seconds.