commit | f7ca8f030a0377454569e84a1c87dccc359b8912 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Feb 02 02:27:54 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Feb 02 02:27:54 2023 +0000 |
tree | 525cb6d5f318afc8e9e95ede4fbdb3d87f0a6c8f | |
parent | e7f6478db28c9817610f89f9a5ec6f300743f4bd [diff] | |
parent | 1d7902fc3046547a3df865135b51049ee5e6cb97 [diff] |
Snap for 9552483 from 1d7902fc3046547a3df865135b51049ee5e6cb97 to udc-release Change-Id: I97188630f6c2f9c2777131ceec718327a0916eeb
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.