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.

Sign up for GitHub

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

document procedure to kill stale ros2 daemons #185

Merged
merged 5 commits into from
May 29, 2024
Merged

document procedure to kill stale ros2 daemons #185

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a2b7156
document procedure to kill stale ros2 daemons
berndpfrommer May 29, 2024
397ee30
Update README.md
berndpfrommer May 29, 2024
62bea49
Update README.md
berndpfrommer May 29, 2024
fa8e3e3
Update README.md
berndpfrommer May 29, 2024
984aad4
Update README.md
berndpfrommer May 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,14 @@ ros2 run rmw_zenoh_cpp rmw_zenohd

> Note: Without the zenoh router, nodes will not be able to discover each other since multicast discovery is disabled by default in the node's session config. Instead, nodes will receive discovery information about other peers via the zenoh router's gossip functionality. See more information on the session configs [below](#config).

### Clear stale ros2 daemons
berndpfrommer marked this conversation as resolved.
Show resolved Hide resolved
```bash
pkill -9 -f ros && ros2 daemon stop
```
Without this step the ROS2 CLI commands (e.g. ``ros2 node list``) may
berndpfrommer marked this conversation as resolved.
Show resolved Hide resolved
not work properly since they could still be using a ros2 daemon that
berndpfrommer marked this conversation as resolved.
Show resolved Hide resolved
is running on a different RMW.
berndpfrommer marked this conversation as resolved.
Show resolved Hide resolved

### Run the `talker`
```bash
# terminal 2
Expand Down