Sorry - I'm late to the party,..
further up you said it does send the PID to status - then changes to RC2.... surely that means it's finished as you should only get the return code when it's complete ? So there should be nothing to kill ? - (And even if it does send it to status then you can surely grab it quick enough with the status node ?)
Also if it is a python process are you using -u to ensure you are getting unbuffered output ?
The rc2 was coming out of status indicating the process was not running – and I don’t know how to get info out of a node status message (underneath) other than to physically look at it.
The bash solution works.. inject a unique name into an inject node payload along with the stuff to run:
tester python /home/pi/luma.examples/examples/3d_box.py --interface spi --display ssd1351 --height 128 --width 128
In the actual exec node: command is:
bash -c "exec –a
Followed by appending the message payload from the inject, followed by additional arguments
To kill the task, put:
followed by the unique name.
Messy but it works a treat. Unless there’s a simpler way,