Daan De Meyer
581b9db76a
Provide a Tokio-like #[tokio::main] entry point for binaries that want to run their main function inside a fiber on a default sd_event loop. DEFINE_MAIN_FUNCTION_FIBER(impl) mirrors DEFINE_MAIN_FUNCTION but routes impl through a new run_main_fiber() helper. impl keeps the run() convention while the loop's exit code keeps the exit status convention: impl's result never becomes an exit code, an explicit exit status wins over a successful impl, and impl's own failure wins over the exit status unless it is the -ECANCELED of a fiber that the exit request cancelled. Signal policy stays with impl so existing handlers such as sd_event_set_signal_exit() keep working. The fiber is created fire-and-forget: as long as the loop reaches SD_EVENT_FINISHED it unwinds the fiber through its exit event source, so we never hold a reference we cannot drop because the fiber is still suspended. A loop that fails internally never dispatches its exit sources, so the fiber may stay suspended with no working loop left to unwind it; we leak both for now and leave a TODO to keep the broken loop out of the default slot. Since the fiber also refers to run_main_fiber()'s stack frame, refuse to run on a loop we don't own, or from a fiber, as sd_fiber_new() leaves the exit event source disabled there and nothing would unwind the fiber. Cover argument forwarding, result propagation, explicit event exits, nested invocations, signal-source registration, event-loop errors, and fiber stack unwinding, and check after every run that the default event loop was released again. Also build and run a separate test executable that expands DEFINE_MAIN_FUNCTION_FIBER itself and verifies that a positive implementation result maps to a successful process exit.
System and Service Manager
Details
Most documentation is available on systemd's website.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release