summaryrefslogtreecommitdiff
path: root/units/systemd-fsck@.service.in
Commit message (Collapse)AuthorAgeFilesLines
* units: make sure that fsck is executed before quotachecktblume2016-05-101-1/+1
| | | | fsck determines wheter an automatic quotacheck should be executed. Hence fsck service needs to run before quotacheck service.
* fsck: remove fsckd again, but keep the door open for external replacementLennart Poettering2015-04-281-2/+1
| | | | | | | | | | | | | | | | | 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.
* Add fsckd service and socket, retarget systemd-fsckDidier Roche2015-02-181-2/+2
| | | | | systemd-fsckd can be socket-activated by systemd-fsck process. Reflect that in the different unit files.
* readahead: wipe out readaheadDaniel Buch2014-09-251-1/+1
|
* units: order systemd-fsck@.service after local-fs-pre.target.Ivan Shapovalov2014-08-261-1/+1
| | | | | | With this change, it becomes possible to order a unit to activate before any modifications to the file systems. This is especially useful for supporting resume from hibernation.
* fstab-generator: Generate explicit dependencies on systemd-fsck@.service ↵Thomas Bächler2013-10-191-1/+1
| | | | | | | | | instead of using FsckPassNo [tomegun: * order all fsck instances after fsck-root * check for OOM * added notes in the manpages]
* units: make fsck units remain after exitZbigniew Jędrzejewski-Szmek2013-08-151-1/+1
| | | | | | | | Without this, fsck would be re-run if any other service which pulls in a target requiring one of the mounts was started after fsck was done but before the initial transaction was done. https://bugs.freedesktop.org/show_bug.cgi?id=66784
* unit: rename BindTo= to BindsTo=Lennart Poettering2012-07-131-1/+1
| | | | | | | | all other dependencies are in 3rd person. Change BindTo= accordingly to BindsTo=. Of course, the dependency is widely used, hence we parse the old name too for compatibility.
* units: fix Documentation= tag in fsck unitsLennart Poettering2012-06-271-1/+1
|
* man: document systemd-fsckLennart Poettering2012-06-271-0/+1
|
* units: rename fsck@.service to systemd-fsck@.serviceLennart Poettering2012-06-251-0/+20
The rule is that units that encapsulate our own code are prefixed with "systemd-". Since the fsck units invoke our own code, hence add the missing prefix. Since a long long time the fsck units didn't invoke the naked fsck binaries anymore, and it is unlikely that this well ever change. On the opposite: the code in systemd-fsck will probably get more complex over time to handle fsck progress to plymouth forwarding. Same for quotacheck (but not quotaon!)