El 05-11-2018 a las 3:17, piliu escribió:
During this service, the power state can not be got from sysfs, neither
it can be got by systemd's utility. So is it acceptable to signal the
failure of service by a tmp file under /tmp ? I.e adding
FailureAction=touch /tmp/poweroff_fail in
On 11/05/2018 07:42 PM, Cristian Rodríguez wrote:
>
>
> El 01-11-2018 a las 5:34, piliu escribió:
>
>> Any suggestion?
>>
>
> Yeah. Don't..if poweroff fails reboot will too..please attack the root
> cause of this problem.. why the machine fails to poweroff, is it a
> service blocking
El 01-11-2018 a las 5:34, piliu escribió:
Any suggestion?
Yeah. Don't..if poweroff fails reboot will too..please attack the root
cause of this problem.. why the machine fails to poweroff, is it a
service blocking poweroff ? is there a kernel bug ?
On 11/01/2018 05:52 PM, Andrei Borzenkov wrote:
> On Thu, Nov 1, 2018 at 11:34 AM piliu wrote:
>>
>> Hi,
>>
>> I encounter an issue during the poweroff. In my bash script, firstly I
>> use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
>> as a bake up if the poweroff fails.
On Thu, Nov 1, 2018 at 11:34 AM piliu wrote:
>
> Hi,
>
> I encounter an issue during the poweroff. In my bash script, firstly I
> use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
> as a bake up if the poweroff fails. But during tests, many times, the
> machine is rebooted
Am 01.11.18 um 09:34 schrieb piliu:
> I encounter an issue during the poweroff. In my bash script, firstly I
> use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
> as a bake up if the poweroff fails. But during tests, many times, the
> machine is rebooted directly, without
Hi,
I encounter an issue during the poweroff. In my bash script, firstly I
use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
as a bake up if the poweroff fails. But during tests, many times, the
machine is rebooted directly, without waiting for the result of poweroff.
Since