Re: [dev] [ANNOUNCE] slock-1.3

[hiro]

> as well and using a backgrounded `sleep 5; s2ram` before starting slock also
> is
> kind of stupid if slock fails to start up correctly.

How does your integrated execution of s2ram change that?
Your slock can still fail in just the same way.