diff options
| author | Lennart Poettering <lennart@poettering.net> | 2015-04-28 17:13:23 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2015-04-28 17:30:00 +0200 |
| commit | 96d9117ad2db7d8c13f7898127eee8939e88daf1 (patch) | |
| tree | 182c7c733b81452f4099fe4c33a2e3bf060b2051 /man/systemd-fsck@.service.xml | |
| parent | e7a3aa3df640993ce9aace39b946543305f3af53 (diff) | |
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.
Diffstat (limited to 'man/systemd-fsck@.service.xml')
| -rw-r--r-- | man/systemd-fsck@.service.xml | 4 |
1 files changed, 1 insertions, 3 deletions
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.</para> - <para><filename>systemd-fsck</filename> will forward file system - checking progress to <filename>systemd-fsckd.service</filename> - socket. If a file system check fails for a service without + <para>If a file system check fails for a service without <option>nofail</option>, emergency mode is activated, by isolating to <filename>emergency.target</filename>.</para> </refsect1> |