commit | 3bb334989aeb2759180eb85c87fd8b746322d6d4 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Oct 01 16:00:04 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Oct 01 16:00:04 2021 +0000 |
tree | 1dc779d324299f08c5e69538ee554a1cf784f867 | |
parent | aad8ae1c2c3b2280ab21be37c7b07149efeb7b9f [diff] | |
parent | 5d3c93e8fca88207a1d9472991042f160433901d [diff] |
Snap for 7785160 from 5d3c93e8fca88207a1d9472991042f160433901d to t-keystone-qcom-release Change-Id: Id89a2e9625262f1a35b51c743a8cb4a272b40d9e
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.