ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Are you seeing a service persist even after it's been destroyed? The way to "unregister" a service manually is to call shutdown()
on the ServiceServer
(doc here), but this should happen automatically when the ServiceServer
is destroyed. Maybe you're not actually destroying the server object.
2 | No.2 Revision |
Are you seeing a service persist even after it's been destroyed? The way to "unregister" a service manually is to call shutdown()
on the ServiceServer
(doc here), but this should happen automatically when the ServiceServer
object is destroyed. Maybe you're not actually destroying the server object.
3 | No.3 Revision |
Are you seeing a service persist even after it's been destroyed? The way to "unregister" a service manually is to call shutdown()
on the ServiceServer
object (doc here), but this should happen automatically when the ServiceServer
object is destroyed. Maybe you're not actually destroying the server object.
4 | No.4 Revision |
rospy
You can unregister a service by calling shutdown
on the Service
object returned by rospy.Service()
(doc here). It looks like this isn't done automatically on destruction like in the ros c++ implementation. Maybe it should do that.
roscpp
Are you seeing a service persist even after it's been destroyed? The way to "unregister" a service manually is to call shutdown()
on the ServiceServer
object (doc here), but this should happen automatically when the ServiceServer
object is destroyed. Maybe you're not actually destroying the server object.
5 | No.5 Revision |
rospy
You can unregister a service by calling
on the shutdownshutdown()Service
object returned by rospy.Service()
(doc here). It looks like this isn't done automatically on destruction like in the ros c++ implementation. Maybe it should do that.
roscpp
Are you seeing a service persist even after it's been destroyed? The way to "unregister" a service manually is to call shutdown()
on the ServiceServer
object (doc here), but this should happen automatically when the ServiceServer
object is destroyed. Maybe you're not actually destroying the server object.
6 | No.6 Revision |
rospy
You can unregister a service by calling shutdown()
on the
object Servicerospy.Servicereturned by (doc here). It looks like this isn't done automatically on destruction like in the ros c++ implementation. Maybe it should do that. rospy.Service()
roscpp
Are you seeing a service persist even after it's been destroyed? The way to "unregister" a service manually is to call shutdown()
on the ServiceServer
object (doc here), but this should happen automatically when the ServiceServer
object is destroyed. Maybe you're not actually destroying the server object.
7 | No.7 Revision |
rospy
You can unregister a service by calling shutdown()
on the rospy.Service
object (doc here). It looks like this isn't done automatically on destruction like in the ros c++ implementation. Maybe it should do that.
roscpp
Are you seeing a service persist even after it's been destroyed? The way to "unregister" unregister a service manually is to call shutdown()
on the ServiceServer
object (doc here), but this should happen automatically when the ServiceServer
object is destroyed. Maybe you're not actually destroying the server object.