SYSTEM...SERVICE(8)

✨ NAME ✨

okay so bestie, meet systemd-boot-check-no-failures.service (and its lil executable twin, systemd-boot-check-no-failures) — it's the vibe-check queen whose whole job is verifying that your system booted up cleanly. 💖

---

🎀 SYNOPSIS 🎀

systemd-boot-check-no-failures.service

/usr/lib/systemd/systemd-boot-check-no-failures

---

🦋 DESCRIPTION 🦋

so systemd-boot-check-no-failures.service is a system service, right, and what it does is check whether the system booted up successfully. that's it. that's the whole thing. 💅

and ngl the test it runs is so minimal — literally the only thing it asks is: are there any failed units on the system? that's the entire criteria. no cap.

this service is disabled by default, so it's not out here doing anything unless you invite it. but when you do enable it, it gets ordered before boot-complete.target, which means — and this is the iconic part — that target literally cannot be reached when the system booted up with failed services. she said "you're not passing go, you're not reaching the target, periodt." 👑

⚠️ real talk though: because this check is so simple in nature, it's probably not suitable for deployment in most scenarios. it's primarily useful only as an example for developing more fine-grained checks to order before boot-complete.target. so like, she's a demo, she's a muse, she's a starting point — not your production bouncer. 🙈

---

🌈 SEE ALSO 🌈

• systemd(1)
• systemd.special(7)

---

and that's the whole page, bestie 🫶 this was the systemd 262.1 manual, section 8 (system administration commands, iykyk) 💖 go forth and check your boot like the main character you are ✨💅