Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shutdown command is not completely killing the processes. #23880

Open
rajeev-gupta-bashrc opened this issue Nov 1, 2024 · 4 comments
Open

shutdown command is not completely killing the processes. #23880

rajeev-gupta-bashrc opened this issue Nov 1, 2024 · 4 comments

Comments

@rajeev-gupta-bashrc
Copy link

rajeev-gupta-bashrc commented Nov 1, 2024

In the gazebo simulation the shutdown command doesn't kills the gz server, and the gazebo gui remains open with the terminal being unresponsive. If we further kill the background processes by ctrl+c then gazebo doesn't open for the next time. We need to restart the pc (this restarting issue is related to gazebo/gz-server if we don't properly kill the gz-server).

@rajeev-gupta-bashrc
Copy link
Author

rajeev-gupta-bashrc commented Nov 1, 2024

@dakejahl
Copy link
Contributor

dakejahl commented Nov 5, 2024

why not just use ctrl+c?

@rajeev-gupta-bashrc
Copy link
Author

@dakejahl actually we wanted to automate the launch and shut down process, that's why ctrl+c wasn't an option for us. We feed the kill command and it kills the process.
Thank you for looking into it. If you can suggest some changes, we welcome you.

@dakejahl
Copy link
Contributor

dakejahl commented Nov 6, 2024

@rajeev-gupta-bashrc if you're automating the launch/shutdown you can just kill the process from your own scripts? Ctrl+C is just sending SIGINT. I don't think adding a pkill -f to the cpp code is the right place to do it.

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

No branches or pull requests

2 participants