Not sure I fully understand the question. rosnode cleanup removes the registration from the master. This effectively prevents any new subscribers from connecting to the publisher, but will not disturb existing connections. It does nothing else to the node. rosnode kill attempts to kill a node, but it may not work on unresponsive nodes. FYI: we're working on extending roslaunch to provide the ability to use the roslaunch infrastructure to kill nodes on remote machines. - Ken On Wed, Apr 14, 2010 at 12:31 AM, koen buys wrote: > What if a node doens't respond but still is publishing? > > On 13 April 2010 16:49, Brian Gerkey wrote: >> >> On Tue, Apr 13, 2010 at 1:22 AM, Rosen Diankov >> wrote: >> > If processes immediately die without properly calling the ros shutdown >> > methods, the node will stay registered with the core forever. the >> > result is that the rxgraph slowly gets cluttered with dead nodes and >> > makes it really inconvenient. we've tried 'rosnode kill', but that >> > doesn't seem to un-register the node. because we want to keep a >> > roscore constantly running on every robot, we cannot just restart the >> > roscore.... >> >> hi Rosen, >> >> You can try the semi-hidden 'cleanup' feature of rosnode: >>  rosnode cleanup >> It will ping all nodes, then offer to delete entries from the master >> that correspond to the nodes that don't respond. >> >>        brian. >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users > > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > >