You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that for cpp nodes, some info logs are not displayed when running "journalctl -f" and only appear as a huge accumulated block after killing the node. Is this a known bug? And is there a way to fix it?
The text was updated successfully, but these errors were encountered:
Hi Jochen, yes I managed to single out the commit that fixes the problem, forwarding all logs from ROS nodes to journalctl. But even the commit says it is a "hack" since it also forwards logs from nodes started manually with roslaunch to journalctl. Did you guys figure out any other way to make it play nice with journalctl?
I noticed that for cpp nodes, some info logs are not displayed when running "journalctl -f" and only appear as a huge accumulated block after killing the node. Is this a known bug? And is there a way to fix it?
The text was updated successfully, but these errors were encountered: