From aa2cd76c58dfc8622679414db062ade296f5e08b Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Sat, 3 Jul 2021 21:28:17 +0200 Subject: [PATCH] restore daemon: use millisecond log resolution During startup most of the stuff is happening in milliseconds (or less), so the timestamp granularity of seconds made it hard to tell if the previous command required 990ms or 1ms, which is quite the difference in the restore daemon context. Using micros seems not to bring too much additional information, a millisecond is already an ok lower time resolution for logging, so switch only to millis for now. Signed-off-by: Thomas Lamprecht (cherry picked from commit ecd66ecaf6fbf6f929f81a837df25757b6e7a290) Signed-off-by: Thomas Lamprecht --- src/bin/proxmox-restore-daemon.rs | 1 + 1 file changed, 1 insertion(+) diff --git a/src/bin/proxmox-restore-daemon.rs b/src/bin/proxmox-restore-daemon.rs index 8082cca2..7d1d8562 100644 --- a/src/bin/proxmox-restore-daemon.rs +++ b/src/bin/proxmox-restore-daemon.rs @@ -47,6 +47,7 @@ fn main() -> Result<(), Error> { // stdout to a serial terminal attached by QEMU) env_logger::from_env(env_logger::Env::default().default_filter_or("info")) .write_style(env_logger::WriteStyle::Never) + .format_timestamp_millis() .init(); // the API may save some stuff there, e.g., the memcon tracking file