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

RFC: Circular log buffer #7446

Closed
bergzand opened this issue Aug 6, 2017 · 3 comments
Closed

RFC: Circular log buffer #7446

bergzand opened this issue Aug 6, 2017 · 3 comments
Assignees
Labels
Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@bergzand
Copy link
Member

bergzand commented Aug 6, 2017

While testing something out, I got a bit annoyed by uhcpc spewing log messages directly in my serial console 😞.
I was thinking that on nodes with a bit of ram to spare, a circular log buffer would be a valuable addition. a KB of ram dedicated to log messages, set up as a circular log buffer. This could then be read out by a shell command or even over CoAP in environments where there is no shell access.

@jnohlgard
Copy link
Member

Kind of like syslog with logrotate on Linux? I like this idea, especially being blue to read the log through coap or even through the debugger when trying to fix UART issues 👍

@bergzand
Copy link
Member Author

bergzand commented Aug 8, 2017

Yes, the linux kernel log (dmesg) might be the better analogy, but the idea is clear.

I also think that if this project is going to support slipmux, this might be the way to do the message logging.

@miri64 miri64 added Feature Request Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR labels Oct 25, 2017
@miri64 miri64 added Type: new feature The issue requests / The PR implemements a new feature for RIOT and removed Feature Request labels Sep 30, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this as completed Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

No branches or pull requests

4 participants