commit | c727b206a21d70f0bf0754fc929a41e4bf26df5f | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jan 31 01:50:44 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jan 31 01:50:44 2022 +0000 |
tree | fd087aeaa9471b3c5ed13408f8cdeda713b1886b | |
parent | 1dab2e95bdbdb007fa0530bd269ee068d0e8071e [diff] | |
parent | bbf86e7972aaeeb31d4c5dd989ca50c3b5681ff3 [diff] |
Snap for 8133678 from bbf86e7972aaeeb31d4c5dd989ca50c3b5681ff3 to t-keystone-qcom-release Change-Id: I9cf46603fb4dbbad5f872e7cf3a546da322171df
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.