Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Roslaunch without Rosout

asked 2011-05-25 20:44:03 -0600

Daniel Stonier
3145 ●24 ●51 ●64

We're often running off some slow-to-write filesystems, so want to minimise logging once we're out in the wild...but still want some logging so that problems can be investigated after the fact.

Subsequently it would be good if we could avoid duplicating alot of the logging - once is sufficient even if its spread across multiple files. i.e. no aggregated rosout log and no stdout log either.

I'm not sure about the stdout log, but I can comment rosout in roslaunch/roscore.xml. Are there any side effects to doing this? And is there sufficient interest to consider proposing this as an optional argument to roslaunch?

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2011-05-26 04:40:56 -0600

kwc
12244 ●54 ●90 ●132 http://kwc.org/

Modifying the roscore.xml is fine -- that's what it's there for.

Right now there is no option to disable logging in roslaunch. I'd entertain suggestions (in ticket form) of potential ways to enable this (i.e. command-line syntaxes, environment variables, config files, etc...).

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2011-05-25 20:44:03 -0600

Seen: 1,502 times

Last updated: May 26 '11

Roslaunch without Rosout edit

1 Answer

Question Tools

Stats

Related questions

Roslaunch without Rosout