his feature and systemd can rely on a timeout
killing the job if it does not stop within x seconds. But it would be good if
the start / stop protocol allows for it when a notify part is developed.
After all if the system is running on the UPS batteries after a power failure
and the
towards
a stopped state or hung in the getting there.
>From the past I have seen things go wrong in communication when the only thing
>reported back is "I am busy" while there was no progress being made toward the
>finish.
Is this something the systemd team has already put on the to
developments, if not
I need to post that topic somewhere else.
Bonno Bloksma
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi,
Quoting a part of a discussion in debian-user that may be of interest to you .
Bonno Bloksma
-Oorspronkelijk bericht-
Van: Bonno Bloksma
Verzonden: vrijdag 15 augustus 2014 11:20
Aan: debian-u...@lists.debian.org
Onderwerp: RE: systemd fails to poweroff - "A stop job is runnin
