-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Spawn rosbridge in new shell to connect to a roscore #186
Comments
only spawn a new shell for rosbridge to reside at. |
updated to be on rosmod's end. no long need to deal with roslib interaction, which is handled in rosmct |
Need to figure out how to properly manage rosbridge_server's lifecycle (so we can kill it when we |
…el; stop experiment kills it, but there is still another spawned process that needs to be killed.
ocal host also needs to export ROS_IP to the ip address reachable by hosts in the system. Need for roscore to arbitrate pub/sub advertisements correctly |
Will have to update the plugin so that the plugin can know by what IP the ROSMOD system can reach the rosmod server (esp. since the server can and usually does have more than one set of IP addresses) |
From @dwatkins on November 2, 2017 17:4
Spawn a worker process to contain rosbridge and roslib interfaces for each roscore.
Rosbridge needs to run in a new shell for each roscore.
Needs to:
Copied from original issue: rosmod/rosmct#2
The text was updated successfully, but these errors were encountered: