| commit | 70aba75a027709ebadc8e5173a757dc2e6505c70 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Dec 26 10:03:58 2021 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Dec 26 10:03:58 2021 +0000 |
| tree | fd087aeaa9471b3c5ed13408f8cdeda713b1886b | |
| parent | 27850b3045d597db9cfb36df84bd87e163c36c49 [diff] | |
| parent | 0f803e21ea82f291a2c91ca326bf43afe3d4544d [diff] |
Snap for 8029350 from 0f803e21ea82f291a2c91ca326bf43afe3d4544d to main-cg-testing-release Change-Id: I02bad6d8b29897226c6a77719456f5752facad47
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.