Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider providing user control of log file base names #380

Open
sea-bass opened this issue Sep 29, 2023 · 0 comments
Open

Consider providing user control of log file base names #380

sea-bass opened this issue Sep 29, 2023 · 0 comments
Labels
backlog help wanted Extra attention is needed

Comments

@sea-bass
Copy link

Feature request

Feature description

I have reported an issue in the ros2cli repo recently (ros2/ros2cli#856) which hopefully will gain traction.

The general idea in the above issue -- and please read that for more details -- is that the default log file names right now are prepended with the executable name (in the C++ case) or the Python executable name (e.g., python3) in the Python case.

The investigation is leading to maybe providing a user-configurable parameter for ros2 run that allows the user to provide their own base name for log files.

Per @fujitatomoya's suggestion, I wanted to open this up here as well to ensure that the launch_ros tools track the above issue and have a way to expose this through ros2 launch, and the launch APIs, as well.

@sloretz sloretz added help wanted Extra attention is needed backlog labels Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants