<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Please add "-f" to shutdown to skip fsck on demand" href="https://bugs.freedesktop.org/show_bug.cgi?id=88330#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Please add "-f" to shutdown to skip fsck on demand" href="https://bugs.freedesktop.org/show_bug.cgi?id=88330">bug 88330</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>if there's need to use this option, then this is probably because one has the suspicion that the there's something wrong with the fs. In such a case it is the worst idea of all to make a change to the file system by touching a file in /. Asking for a file system fix by writing to it is really really wrong. Moreover, doing this is not possible in setups where / is mounted read-only. Hence, this sysv feature is actively dangerous and cannot cover all usecase, as such I am very strongly opposed to adding support for this to systemd natively. We shouldn't support functionality that is really obviously broken at a dangerous level, even if it traditionally was supported on sysv. Sorry! That said, it's not particularly hard to manually touch /forcefsck and then reboot. A "-f" switch is only marginally easier anyway. Hence not supporting this in systemd itself is not too much of a loss if people really really want to use it. I really want to avoid "blessing" something by supporting it in systemd natively, that it so obviously dangerous. Sorry!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>