Bug#749832: systemd: ignores /run/do-not-hibernate, hibernates after kernel update

[Zbigniew Jędrzejewski-Szmek]

On Fri, May 30, 2014 at 09:00:12PM -0700, Nikolaus Rath wrote:
> On 05/30/2014 10:46 AM, Michael Biebl wrote:
> > Am 30.05.2014 18:34, schrieb Nikolaus Rath:
> >>>
> >>> The problem with simply doing nothing on hibernate when
> >>> /run/do-not-hibernate exists, is that this is also not visible to the
> >>> user since there there is no API to communicate that to the user why
> >>> hibernate did not succeed.
> >>
> >> Well, in my case I'm calling 'systemctl hibernate' from the command
> >> line, so a simple message to the console would do.
> > 
> > Do you want to work on such a patch?
> > You'd have to implement this check in systemd (or logind) and then
> > communicate the failure reason back to the caller.
> > That requires updates to the D-Bus interface etc.
> 
> Sorry, no. I'm not familiar with D-Bus at all. I'll just create wrapper
> script for systemctl hibernate that does the check, and I assume that's
> not quite suitable for inclusion in the Debian package...
It'd be easier and more worthwhile I think, to work from the other and
and instruct the packaging scripts to also take a hibernation inhibitor.
This would have the advantage that other tools which already know how
to deal with inhibitor locks would be able to notify the user etc.
Something like 'systemd-inhibit --what sleep sleep 10000', but smarter.
It seems that the inhibitor api is not flexible enough here, though,
so some upstream discussion would be required.

Zbyszek