[systemd-devel] [PATCH 2/8] man/systemd.timer.xml: improve documentation of WakeSystem=

[Zbigniew Jędrzejewski-Szmek]

On Fri, Feb 20, 2015 at 02:30:59PM -0800, Shawn Landden wrote:
> ---
>  man/systemd.timer.xml | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
> index 20890f2..4207be0 100644
> --- a/man/systemd.timer.xml
> +++ b/man/systemd.timer.xml
> @@ -230,8 +230,9 @@
>          be suspended and if the system supports this. Note that this
>          option will only make sure the system resumes on the
>          appropriate times, it will not take care of suspending it
> -        again after any work that is to be done is finished. Defaults
> -        to <varname>false</varname>.</para></listitem>
> +        again after any work that is to be done is finished. (For that
> +        use <varname>ExecStartPost=systemd-suspend.service</varname> in the triggered Unit=)
> +        Defaults to <varname>false</varname>.</para></listitem>
I don't think that this approach is a good idea. The problem is that
between the time where the wakeup happened and the job is finished,
the user might have woken up too and started using the machine. Then
at a random (for the user) point, the machine starts shutting down.
I think we should be striving towards suspend-on-idle or poweroff-on-idle,
without hardcoding behaviour in this way.

There's alos the problem that ExecStartPost takes commands, not unit
names, so this cannot work as written.

Zbyszek