| commit | 7803608833fd0246186a5c1a4737654ccbb416a5 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Dec 16 02:07:09 2021 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Dec 16 02:07:09 2021 +0000 |
| tree | fd087aeaa9471b3c5ed13408f8cdeda713b1886b | |
| parent | e819f786b7ef78aff5a21195e2ae0b3a8181ddfc [diff] | |
| parent | 515fb336128e64969782d50c2017c80c4b1cea33 [diff] |
Snap for 8006021 from 515fb336128e64969782d50c2017c80c4b1cea33 to tm-release Change-Id: Iadc8aa120800f7fcdb85284e25d4ab36ef947a40
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.