Roslaunch without Rosout
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?
add a comment
