From b167e20899f51b8d3e68f4fca34e1855ef464c05 Mon Sep 17 00:00:00 2001 From: Admin Pupkin Date: Mon, 1 Jun 2026 09:20:45 +0300 Subject: [PATCH] fix: revert coretempd service type to oneshot_async MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit coretempd uses syscall::call::write() for init notification, which sends raw bytes — not an fd transfer via CallFlags::FD that the Scheme init type expects. Changing to Scheme would cause init to block forever in call_ro waiting for an fd that never arrives in the expected format. The oneshot_async + resilience pattern is correct for coretempd. --- config/redbear-device-services.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/redbear-device-services.toml b/config/redbear-device-services.toml index d95e69dcec..feb7ed0b19 100644 --- a/config/redbear-device-services.toml +++ b/config/redbear-device-services.toml @@ -484,7 +484,7 @@ requires_weak = ["04_drivers.target"] [service] cmd = "/usr/bin/coretempd" -type = { scheme = "coretemp" } +type = "oneshot_async" """ [[files]]