Cleanup map and console after controlling terminal dies #739
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MAVProxy currently doesn't kill its map and console when the controlling tty dies. I suspect this is because multiple SIGHUPs are sent. You can test this behavior by executing mavproxy.py in xterm (xterm -hold -e mavproxy.py --map --console) and then killing the xterm process itself. You could also run mavproxy.py in a tmux pane and kill the pane.
Also, this fixes the map and console persisting when the main mavproxy.py has its input stream closed via ^D.