systemd: Diagnose Unit Dependency and Ordering Failures

systemd: Diagnose Unit Dependency and Ordering Failures

Choose one answer. All questions are included, with explanations after checking. No time limit. Training target: 28/34. Applied systemd dependency graphs: pull-in versus ordering; failed and condition-skipped starts; Requires, Wants, Requisite, BindsTo, PartOf and Conflicts; stop direction; enablement; service readiness; cycles and read-only diagnostics. Not a full Linux administration exam. Each scenario states its relevant jobs and relationships; no unstated relationship changes the described outcome. Sources: https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html https://www.freedesktop.org/software/systemd/man/latest/systemctl.html https://www.freedesktop.org/software/systemd/man/latest/systemd-analyze.html
1 из 34
web.service has After=database.service. Both services are active and both receive stop jobs in the same transaction. Which shutdown order follows?