Skip to main content

launch_direct_children

Function launch_direct_children 

Source
pub async fn launch_direct_children(
    targets: &[String],
    iroh_required: bool,
    explicit_config: Option<&Path>,
    exe: &Path,
    spawner: &ProcessSpawner,
) -> Result<()>
Expand description

Launch children directly in profile-aware dependency order (#1585).

Shared by service start --daemon, no-systemd service start, and the no-systemd service install --start fallback, so every direct launch gets the same ordering, config forwarding, and readiness contract.

Required-native: every child must report genuine readiness before the next child (and stage) starts; any spawn, early-exit, or timeout failure stops already-started children in reverse start order and returns Err — the caller never prints success for a partial launch. Compatibility keeps the historical best-effort behavior (per-service error lines, UDS-presence stage barrier with warn-and-continue) so existing deployments are unchanged.