| commit | 53052e3f79655da1403ba76702003f84279ed6c5 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Jun 19 04:32:32 2022 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Jun 19 04:32:32 2022 +0000 |
| tree | fd087aeaa9471b3c5ed13408f8cdeda713b1886b | |
| parent | d3a818e985036524e42e32edcaac207a442ff36e [diff] | |
| parent | 8aea471660ec8232a134779e88ba884f5ab63219 [diff] |
Snap for 8743232 from 8aea471660ec8232a134779e88ba884f5ab63219 to gki13-boot-release Change-Id: Id044cfaf2f6779ae677ff48a86289ee84c914d37
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.