| commit | 94925501a1016aab74b9684cb6b1173431d18bdb | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Mar 07 02:15:30 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Mar 07 02:15:30 2024 +0000 |
| tree | 6a270d1abff0a8e78af1156a28369f5f6a75acd8 | |
| parent | 363900875aec7b952f965960e83be505b43a6003 [diff] | |
| parent | 6c2a039de562f39f1d45ac58f9d0cf80ad3ed8f4 [diff] |
Snap for 11541002 from 6c2a039de562f39f1d45ac58f9d0cf80ad3ed8f4 to sdk-release Change-Id: Ifd692d59b9eb83d5f73502d9c15e05582ae267e4
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.