I think that would be non-trivial given the way this plugin executes commands. This plugin does not use an interactive shell, instead it passes a command to the server and awaits a response indicating a return code. Because of that, it would not be able to interrupt the remote process without passing another command to do so. Even in that instance, you would have to know the PID of the remote command.
John Tatum
added a comment - I think that would be non-trivial given the way this plugin executes commands. This plugin does not use an interactive shell, instead it passes a command to the server and awaits a response indicating a return code. Because of that, it would not be able to interrupt the remote process without passing another command to do so. Even in that instance, you would have to know the PID of the remote command.
I think that would be non-trivial given the way this plugin executes commands. This plugin does not use an interactive shell, instead it passes a command to the server and awaits a response indicating a return code. Because of that, it would not be able to interrupt the remote process without passing another command to do so. Even in that instance, you would have to know the PID of the remote command.