Skip to content
This repository has been archived by the owner on Jul 3, 2019. It is now read-only.

Ensure robocluster has a kill switch #10

Open
ottopasuuna opened this issue Sep 13, 2017 · 2 comments
Open

Ensure robocluster has a kill switch #10

ottopasuuna opened this issue Sep 13, 2017 · 2 comments

Comments

@ottopasuuna
Copy link
Member

If something goes wrong during the operation of the rover and we need to shut everything down,
a kill command from the master node should ensure every process on the system is stopped immediately.

@jpas
Copy link
Contributor

jpas commented Sep 14, 2017

Should this be a dead-man's switch?

@ottopasuuna
Copy link
Member Author

Possibly, I think It would probably be more annoying than practical though. The issue isn't the operator not paying attention, but the rover not doing what the operator is telling it to do.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants