commit | 1dab2e95bdbdb007fa0530bd269ee068d0e8071e | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Oct 28 17:30:02 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Oct 28 17:30:02 2021 +0000 |
tree | 6aa1509501d7a22d621399ad6cfff18ddba73902 | |
parent | 3bb334989aeb2759180eb85c87fd8b746322d6d4 [diff] | |
parent | 26631ec55ac078b0e3038a8d020800756e925e5b [diff] |
Snap for 7862349 from 26631ec55ac078b0e3038a8d020800756e925e5b to t-keystone-qcom-release Change-Id: I432fb310ed4dbc6f9cace30d44fe8007f491c07b
Logger implementation for low level kernel log (using /dev/kmsg
)
Usually intended for low level implementations, like systemd generators, which have to use /dev/kmsg
:
Since syslog is not available (see above) write log messages to /dev/kmsg instead.
[dependencies] log = "0.4" kernlog = "0.3"
#[macro_use] extern crate log; extern crate kernlog; fn main() { kernlog::init().unwrap(); warn!("something strange happened"); }
Note you have to have permissions to write to /dev/kmsg
, which normal users (not root) usually don't.