From a108fcbacee859036f5613177321889bc34fd597 Mon Sep 17 00:00:00 2001 From: Florian Klink Date: Thu, 13 Apr 2023 22:54:54 +0200 Subject: fsck: look for fsck binary not just in /sbin This removes remaining hardcoded occurences of `/sbin/fsck`, and instead uses `find_executable` to find `fsck`. We also use `fsck_exists_for_fstype` to check for the `fsck.*` executable, which also checks in `$PATH`, so it's fair to assume fsck itself is also available. --- man/systemd-fsck@.service.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'man') diff --git a/man/systemd-fsck@.service.xml b/man/systemd-fsck@.service.xml index e928aebdb3..403286829e 100644 --- a/man/systemd-fsck@.service.xml +++ b/man/systemd-fsck@.service.xml @@ -51,17 +51,17 @@ systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem type - (/sbin/fsck.type). These checkers will decide if + (fsck.type). These checkers will decide if the filesystem should actually be checked based on the time since last check, number of mounts, unclean unmount, etc. systemd-fsck-root.service and systemd-fsck-usr.service - will activate reboot.target if /sbin/fsck returns the "System - should reboot" condition, or emergency.target if /sbin/fsck + will activate reboot.target if fsck returns the "System + should reboot" condition, or emergency.target if fsck returns the "Filesystem errors left uncorrected" condition. systemd-fsck@.service will fail if - /sbin/fsck returns with either "System should reboot" + fsck returns with either "System should reboot" or "Filesystem errors left uncorrected" conditions. For filesystems listed in /etc/fstab without nofail or noauto options, local-fs.target -- cgit v1.2.1