Bug#776997: systemd-sysv's shutdown can not handle all parameters / arguments

Michael Biebl biebl at debian.org
Tue Feb 3 22:37:03 GMT 2015


control: severity -1 minor
control: tags -1 wontfix

Am 03.02.2015 um 23:24 schrieb Lars Cebulla:
> Package: systemd-sysv
> Version: 215-10
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
> 
>         Try to force a fsck after reboot by typing
>         # shutdown -r -F now
> 
>         (is valid with "normal" shutdown and described in manpage)
> 
>    * What was the outcome of this action?
> 
>         "systemctl" told me it is an unhandled option:
> 
>         Code should not be reached 'Unhandled option' at
> .../src/systemctl/systemctl.c:6316, function shutdown_parse_argv(). Aborting.
>         Abgebrochen
> 
>    * What outcome did you expect instead?
> 
>         System should reboot and perform a fsck without any errors !

The man page coming with systemd-sysv does not document that command
line option. Are you perhaps using a translation which incorrectly
points at the sysv counterpart?

If you want to force an fsck on next boot, please add fsck.mode=force to
the kernel command line (see man systemd-fsck at .service).

systemd intentionally doesn't write a /force.fsck flag file to the disk
to achieve that. You typically want to avoid writing to a file system if
you are concerned about it's consistency. That's why the -F parameter is
not supported (and won't be added).



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150203/62cc8428/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list