Your message dated Sat, 28 Nov 2015 22:41:25 +0100
with message-id <[email protected]>
and subject line Re: Bug#806533: systemd-sysv: /sbin/shutdown is missing -F
option (force fsck on reboot)
has caused the Debian Bug report #806533,
regarding systemd-sysv: /sbin/shutdown is missing -F option (force fsck on
reboot)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
806533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806533
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-sysv
Version: 228-2
Severity: important
This option seems to have recently disappeared; see here, for example:
http://linuxcommand.org/man_pages/shutdown8.html
It seems to be related to systemd; perhaps it's supposed to be an
"improvement".
http://forums.fedoraforum.org/showthread.php?t=268935
There are a wide variety of situations in which you might want to force
filesystem checks on reboot, which is why this option existed in the first
place. There is no valid reason for removing it -- it's OPTIONAL.
Can we please have it back?
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd-sysv depends on:
ii systemd 228-2
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Dear Ian,
Am 28.11.2015 um 15:48 schrieb Ian Bruce:
> This option seems to have recently disappeared; see here, for example:
>
> http://linuxcommand.org/man_pages/shutdown8.html
The man page shipped by systemd is a different one and doesn't list -F
as an option, because...
> It seems to be related to systemd; perhaps it's supposed to be an
> "improvement".
>
> http://forums.fedoraforum.org/showthread.php?t=268935
>
> There are a wide variety of situations in which you might want to force
> filesystem checks on reboot, which is why this option existed in the first
> place. There is no valid reason for removing it -- it's OPTIONAL.
>
> Can we please have it back?
it was removed on purpose. -F creates a flag file on the file system
which should be checked. For a file system which potentially already has
issues, doing a write is probably not a good idea.
Systemd still has legacy support for /forcefsck. So if you create that
file manually, systemd will respect that. You need to do that by hand
though. The reasoning here is, to make the user aware that this causes a
write operation on the file system, the -F switch hides that.
That said, touch /forcefsck is discouraged and a better mechanism is to
pass systemd.fsck=force on the kernel command line.
For more details, see man [email protected].
In summary, the change is deliberate and there exist better
alternatives. Thus closing this bug report.
Regards,
Michael
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
