ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

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.

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.

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.

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.

rospy

You can unregister a service by calling shutdownshutdown() 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.

rospy

You can unregister a service by calling shutdown() on the Servicerospy.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.

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.