Re: [dev] [ANNOUNCE] slock-1.3
> 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.
Received on Sat Feb 13 2016 - 01:27:15 CET
This archive was generated by hypermail 2.3.0
: Sat Feb 13 2016 - 01:36:09 CET