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
core: tools: linux2rest: Update to v0.5.4 #2446
core: tools: linux2rest: Update to v0.5.4 #2446
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- We need to update the command-line to add the log settings in the PR, without it, it'll just not run.
I was testing with --log-system netstat=10,platform=10,serial-ports=10,system-cpu=10,system-disk=30,system-info=10,system-memory=10,system-network=10,system-process=10,system-temperature=10,system-unix-time-seconds=10
-
The BlueOS system-information frontend seems to be failing to get the temperature:
-
Keep in mind that CPU peaks might be a little high for the max frequencies:
linux2rest_cpu_usage_peaks_almost_30_percent.mp4
- The .log (wrongly named) contains no logged data, just warn/info messages.
28b6674
to
85d1e8c
Compare
@joaoantoniocardoso the filename should be fixed now. |
I meant.. if we merged this as it was, there would be no linux2rest running. It was panicking |
85d1e8c
to
eacb128
Compare
This new version follows the same log structure as mavlink-camera-manager and also allows the user to log custom system information Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
eacb128
to
eb1c6f4
Compare
@joaoantoniocardoso thanks for pointing, indeed it was crashing. This final version should have everything fixed. |
This new version follows the same log structure as mavlink-camera-manager and also allows the user to log custom system information