commit | 8ce9a26ec975de8aad4de32fdea6f36194e1c756 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed May 10 16:17:49 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed May 10 16:17:49 2023 +0000 |
tree | 628d73140d42906c0980caef76ec1933b5ab0a97 | |
parent | ae3911416e83806094e81707c90887c0d3d161bd [diff] | |
parent | 6f4e81a47e1825bd679b89b9df9582744ffb1e94 [diff] |
Snap for 10103804 from 6f4e81a47e1825bd679b89b9df9582744ffb1e94 to mainline-tzdata5-release Change-Id: Ic70d6e0297d4f53349a6dca406ddb50d87ca6594
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.