Much simpler change than anticipated! I think it was a combination of a typo in shm_stop.service and me adding more Before and After dependencies to the services.
Changed type of net_handler, dev_handler, and executor services to "simple"
Listed shm_start.service as an OnFailure dependency of shm_stop (I think this was a typo before)
Was working on a different solution before and added some comments to run.sh
I tested this and it does seem to work, if you try killing one of the processes using kill -6, it instantaneously regenerates a new instance of Runtime. The change from oneshot to simple is more of an aesthetic thing; when the processes are running now and you do systemctl status executor, for example, it will display active (running) as its status in bold green, which is pretty satisfying :P
If you want to stop Runtime completely, doing sudo systemctl stop dev_handler (or executor or net_handler) followed by rm /dev/shm/* works (stopping those services doesn't automatically trigger shm_stop.service--you have to do that manually).
Much simpler change than anticipated! I think it was a combination of a typo in
shm_stop.serviceand me adding moreBeforeandAfterdependencies to the services.simple"shm_start.serviceas anOnFailuredependency ofshm_stop(I think this was a typo before)run.shI tested this and it does seem to work, if you try killing one of the processes using
kill -6, it instantaneously regenerates a new instance of Runtime. The change fromoneshottosimpleis more of an aesthetic thing; when the processes are running now and you dosystemctl status executor, for example, it will displayactive (running)as its status in bold green, which is pretty satisfying :PIf you want to stop Runtime completely, doing
sudo systemctl stop dev_handler(orexecutorornet_handler) followed byrm /dev/shm/*works (stopping those services doesn't automatically triggershm_stop.service--you have to do that manually).Closes #144