Red Hat Bugzilla – Bug 799574
Cannot cancel fsck
Last modified: 2012-10-30 14:11:42 EDT
With sysv or upstart, an fsck can normally be canceled with C or CTRL+C.
No such functionality exists for systemd and is quite frustrating since I mount my drives in weird ways.
You can edit /usr/lib/systemd/system/fsck@.service and add line StandardInput=tty, thus stdin of fsck will be connected to /dev/console (default unless in TTYPath= specified otherwise) and then pressing C-c should cancel filesystem check.
Any particular reason why we simply dont just default to this?
This is up to Lennart to decide, however I'm not sure this was default with upstart, as stated in Description. It could be done by setting 'console owner' instead of 'console output' option, thus if this was not default in RHEL6, then I'd say we should leave it as it is now, and it's up to administrator to change it as desired.
Note this bug is filed against Fedora so RHEL behaviour is irrelevant here...
(In reply to comment #2)
> Any particular reason why we simply dont just default to this?
If an fsck is started after boot is complete we really shouldn't try to take posession of /dev/tty1 again, since X11 or a getty might run on it, and things would get very confused if we'd try to read input from that.
*** This bug has been marked as a duplicate of bug 719952 ***