commit | 9c45e853f7a2e794f8fe4b04e49e13bf159190ab | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Aug 25 07:53:38 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Aug 25 07:53:38 2022 +0000 |
tree | fd087aeaa9471b3c5ed13408f8cdeda713b1886b | |
parent | 53052e3f79655da1403ba76702003f84279ed6c5 [diff] | |
parent | e77c3db504a2e541d653949a948a20fb5dfb277b [diff] |
Snap for 8992082 from e77c3db504a2e541d653949a948a20fb5dfb277b to gki13-boot-release Change-Id: I3fcc3666a49742fd2bdff843871cd48dfecced69
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.