Re: How can I force a full fsck on a remote system at next reboot?
On 2015-03-12, Liam O'Toole <liam.p.otoole@gmail.com> wrote:
> On 2015-03-12, Elimar Riesebieter <riesebie@lxtec.de> wrote:
>> * Liam O'Toole <liam.p.otoole@gmail.com> [2015-03-11 20:44 +0000]:
>>
>>> On 2015-03-11, Elimar Riesebieter <riesebie@lxtec.de> wrote:
>> [...]
>>> > According to shutdown(8)
>>> >
>>> > ...
>>> > -f Skip fsck on reboot.
>>> >
>>> > -F Force fsck on reboot.
>>> > ...
>>> >
>>> > Elimar
>>>
>>> Those options are indeed available in the case of the wheezy version of
>>> /sbin/shutdown, which belongs to the sysvinit package.
>>
>> I am running sid / sysvinit here.
>>
>> $ dpkg -l | grep systemd
>> ii libsystemd0:amd64
>>
>> Elimar
>
> Running jessie here, with systemd 215-12. At the time of writing that's
> also the version of systemd in sid. Those options don't appear in the
> man page for shutdown(8), so I'm puzzled by the fact that you can see
> them. What package owns the file /sbin/shutdown on your system?
>
Never mind, I've just seen the explanation elsewhere in this thread.
Sorry for the noise.
--
Liam
Reply to: