[ros-users] cturtle action_server debug statements

Eitan Marder-Eppstein eitan at willowgarage.com
Mon Jul 26 17:32:32 UTC 2010


We normally only enable the DEBUG log level when we're actively testing or
trying to diagnose a problem in a node. Is there any reason that you need to
have the log level for actionlib set to DEBUG? Can you try setting it to
INFO instead to see if that solves your load/logfile problems. If it
doesn't, please let us know as that's a bug for the ROS logging system.

Hope all is well,


On Sat, Jul 24, 2010 at 3:54 AM, Cedric Pradalier <
cedric.pradalier at mavt.ethz.ch> wrote:

> Hi,
> I've just noticed two rospy.logdebug statement in cturtle
> action_server.py and simple_action_server.py:
> In action_server.py:314: rospy.logdebug("Status async");
> In simple_action_server.py:306: rospy.logdebug("SAS: execute");
> On my system, with my simple launch files and simple_action_server,
> these two are making my logfiles grow to infinity, and makes my
> action_server use 10% of my CPU while not doing anything.
> I've commented them out for now, but is there a smarter way?
> For information, I've also noticed that rosout is in general using
> around 10% of my CPU with a slow harddrive (within virtualbox), but that
> it goes down to 4-5% when putting the ROS_LOG_DIR in tmpfs. This might
> be significant for embedded system logging on a flash-drive.
> --
> Dr. Cedric Pradalier
> http://www.asl.ethz.ch/people/cedricp
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20100726/cdc54c9c/attachment-0003.html>

More information about the ros-users mailing list