Files
RedBear-OS/logd/src/main.rs
T
bjorn3 f1057b6750 daemon: Abort on errors
All users did this anyway. And handling it inside the daemon crate
allows avoiding a panic of the parent process when the child process
panicked.
2025-12-03 21:55:47 +01:00

39 lines
998 B
Rust

use redox_scheme::{RequestKind, SignalBehavior, Socket};
use std::process;
use crate::scheme::LogScheme;
mod scheme;
fn daemon(daemon: daemon::Daemon) -> ! {
let socket = Socket::create("log").expect("logd: failed to create log scheme");
daemon.ready();
let mut scheme = LogScheme::new();
while let Some(request) = socket
.next_request(SignalBehavior::Restart)
.expect("logd: failed to read events from log scheme")
{
let request = match request.kind() {
RequestKind::Call(call) => call,
RequestKind::OnClose { id } => {
scheme.on_close(id);
continue;
}
_ => continue,
};
let response = request.handle_sync(&mut scheme);
socket
.write_responses(&[response], SignalBehavior::Restart)
.expect("logd: failed to write responses to log scheme");
}
process::exit(0);
}
fn main() {
daemon::Daemon::new(daemon);
}