From 96d9117ad2db7d8c13f7898127eee8939e88daf1 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 28 Apr 2015 17:13:23 +0200 Subject: fsck: remove fsckd again, but keep the door open for external replacement For a longer discussion see this: http://lists.freedesktop.org/archives/systemd-devel/2015-April/030175.html This introduces /run/systemd/fsck.progress as a simply AF_UNIX/SOCK_STREAM socket. If it exists and is connectable we'll connect fsck's -c switch with it. If external programs want to get progress data they should hence listen on this socket and will get all they need via that socket. To get information about the connecting fsck client they should use SO_PEERCRED. Unless /run/systemd/fsck.progress is around and connectable this change reverts back to v219 behaviour where we'd forward fsck output to /dev/console on our own. --- man/systemd-fsck@.service.xml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'man/systemd-fsck@.service.xml') diff --git a/man/systemd-fsck@.service.xml b/man/systemd-fsck@.service.xml index 69b8fdde2c..e4ffcba168 100644 --- a/man/systemd-fsck@.service.xml +++ b/man/systemd-fsck@.service.xml @@ -80,9 +80,7 @@ the filesystem should actually be checked based on the time since last check, number of mounts, unclean unmount, etc. - systemd-fsck will forward file system - checking progress to systemd-fsckd.service - socket. If a file system check fails for a service without + If a file system check fails for a service without , emergency mode is activated, by isolating to emergency.target. -- cgit v1.2.3