Module control 

Server control from the operator’s desk: the pid file the server writes, the incarnation checks that make it trustworthy, the shutdown outcome record that crosses the process boundary, and the stop flow built on all three. aion server stop / aion server status render these; the logic and its types live here so the server crate owns one truth about its own lifecycle records.

Re-exports

pub use incarnation::IncarnationProbe;

pub use incarnation::SelfIdentity;

pub use outcome::NoteFate;

pub use outcome::OutcomeRecord;

pub use outcome::ParkedWorkerRecord;

pub use pid_file::PidFileGuard;

pub use pid_file::PidRecord;

pub use pid_file::StaleReconciliation;

pub use stop::StopOutcome;

pub use stop::StopRefusal;

pub use stop::StopVerdict;

Modules

incarnation

Incarnation identity: proving that the process wearing a recorded pid is the server that recorded it.

outcome

The shutdown outcome record: how the drain’s rich result crosses the process boundary.

pid_file

The server’s pid file: <AION_HOME>/run/aion-server.pid.

stop

The stop flow behind aion server stop: resolve the pid file, verify the incarnation, signal, wait bounded, and read the drain outcome back from the death note.