Issue aimed
Basically right now there is no way to stop logging during the runtime of roscpp node ,event though using service call one cannot disable logs, they can only change the log level of the node.
So to overcome this issue I have basically added a feature to enable/disable logs for any roscpp node using base service set_logger_level.
Approach
To enable/disable logs, one has to pass enable/disable parameter in logger, part of service request.
Sample Service call to disable loggingrosservice call /node_name/set_logger_level "logger: 'disable' level: 'info'"
This will make sure no logs will get dump.
To enable back logs, one has to pass enable as a logger or ros
Example:
rosservice call /node_name/set_logger_level "logger: 'ros' level: 'info'"
or using enable parameter
rosservice call /node_name/set_logger_level "logger: 'enable' level: 'info'"
In Progress
We have already raised a PR for rospy part, so that any node can be disable using service call.
Issue aimed Basically right now there is no way to stop logging during the runtime of roscpp node ,event though using service call one cannot disable logs, they can only change the log level of the node. So to overcome this issue I have basically added a feature to enable/disable logs for any roscpp node using base service
set_logger_level.Approach To enable/disable logs, one has to pass enable/disable parameter in logger, part of service request. Sample Service call to disable logging
rosservice call /node_name/set_logger_level "logger: 'disable' level: 'info'"This will make sure no logs will get dump.To enable back logs, one has to pass
enableas a logger orrosExample:rosservice call /node_name/set_logger_level "logger: 'ros' level: 'info'"or using enable parameterrosservice call /node_name/set_logger_level "logger: 'enable' level: 'info'"In Progress We have already raised a PR for rospy part, so that any node can be disable using service call.