Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #263716 > unrolled thread

Systemd timer and sleeping laptop

Back to article view | Back to linux.debian.user

Contents

  Systemd timer and sleeping laptop Erwan David <erwan@rail.eu.org> - 2023-11-20 13:10 +0100
    Re: Systemd timer and sleeping laptop Greg Wooledge <greg@wooledge.org> - 2023-11-20 13:30 +0100
      Re: Systemd timer and sleeping laptop Erwan David <erwan@rail.eu.org> - 2023-11-20 14:10 +0100
      Re: Systemd timer and sleeping laptop Cindy Sue Causey <butterflybytes@gmail.com> - 2023-11-20 14:50 +0100
        Re: Systemd timer and sleeping laptop Greg Wooledge <greg@wooledge.org> - 2023-11-20 15:10 +0100
        Re: Systemd timer and sleeping laptop David Wright <deblis@lionunicorn.co.uk> - 2023-11-21 05:10 +0100

#263716 — Systemd timer and sleeping laptop

Hello,


What happens when a timer should have been triggered at a time the 
computer was sleeping ?

I see that wit Persitent=true it is triggered at restart when it should 
have been triggered when the computer was off, but in case of sleep (or 
deeep sleep) the timer unit is not restarted, so what happens ?

[toc] | [next] | [standalone]

#263717

On Mon, Nov 20, 2023 at 12:48:24PM +0100, Erwan David wrote:
> What happens when a timer should have been triggered at a time the computer
> was sleeping ?

systemd.timer(5):

       OnCalendar=
           [...]
           When a system is temporarily put to sleep (i.e. system suspend or
           hibernation) the realtime clock does not pause. When a calendar
           timer elapses while the system is sleeping it will not be acted on
           immediately, but once the system is later resumed it will catch up
           and process all timers that triggered while the system was
           sleeping. Note that if a calendar timer elapsed more than once
           while the system was continously sleeping the timer will only
           result in a single service activation.

[toc] | [prev] | [next] | [standalone]

#263718

Le 20/11/2023 à 13:10, Greg Wooledge a écrit :
> On Mon, Nov 20, 2023 at 12:48:24PM +0100, Erwan David wrote:
>> What happens when a timer should have been triggered at a time the computer
>> was sleeping ?
> systemd.timer(5):
>
>         OnCalendar=
>             [...]
>             When a system is temporarily put to sleep (i.e. system suspend or
>             hibernation) the realtime clock does not pause. When a calendar
>             timer elapses while the system is sleeping it will not be acted on
>             immediately, but once the system is later resumed it will catch up
>             and process all timers that triggered while the system was
>             sleeping. Note that if a calendar timer elapsed more than once
>             while the system was continously sleeping the timer will only
>             result in a single service activation.
>
>
Thanks, I was looking at the wrong place.

-- 
Erwan David

[toc] | [prev] | [next] | [standalone]

#263719

On 11/20/23, Greg Wooledge <greg@wooledge.org> wrote:
> On Mon, Nov 20, 2023 at 12:48:24PM +0100, Erwan David wrote:
>> What happens when a timer should have been triggered at a time the
>> computer
>> was sleeping ?
>
> systemd.timer(5):
>
>        OnCalendar=
>            [...]
>            When a system is temporarily put to sleep (i.e. system suspend
> or
>            hibernation) the realtime clock does not pause. When a calendar
>            timer elapses while the system is sleeping it will not be acted
> on
>            immediately, but once the system is later resumed it will catch
> up
>            and process all timers that triggered while the system was
>            sleeping. Note that if a calendar timer elapsed more than once
>            while the system was continously sleeping the timer will only
>            result in a single service activation.


Speaking as a user who has been "bitten" by this many times, finding a
way to have alarms wake the laptop back up is on my own to-do list. It
just seems like that I played with that type of feature a very long
time ago.

In my usage case, the affected program is alarm-clock-applet. My
experience is that any and all alarms will start going off audibly as
soon as the laptop's lid is lifted post [hibernation]. Since this has
only ever involved bidding on auctions (aka spending money), finding a
work-around has never had high priority on that to-do list, lol.

As an afterthought, it came to mind that one of the video players at
least used to let users toggle an option to keep a laptop from going
to sleep until after a video, e.g. a long movie, stopped playing. That
inspired an "apt-cache search wake from" search for some reason.

That highly generic query only received 10 results for Trixie. Maybe
there's still something in there that's useful. Two of those results,
etherwake and nvram-wakeup, look interesting. Since they already exist
as packages, they must be being used somewhere... which might help
short track figuring out how to apply them to one's own computing
needs.

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#263720

On Mon, Nov 20, 2023 at 08:24:11AM -0500, Cindy Sue Causey wrote:
> Speaking as a user who has been "bitten" by this many times, finding a
> way to have alarms wake the laptop back up is on my own to-do list.

Well then, here's the rest of that paragraph, which I didn't include in
the previous message:

           If WakeSystem= (see below)
           is enabled a calendar time event elapsing while the system is
           suspended will cause the system to wake up (under the condition the
           system's hardware supports time-triggered wake-up functionality).

[toc] | [prev] | [next] | [standalone]

#263747

On Mon 20 Nov 2023 at 08:24:11 (-0500), Cindy Sue Causey wrote:
[ … ]
> inspired an "apt-cache search wake from" search for some reason.
> 
> That highly generic query only received 10 results for Trixie. Maybe
> there's still something in there that's useful. Two of those results,
> etherwake and nvram-wakeup, look interesting. Since they already exist
> as packages, they must be being used somewhere... which might help
> short track figuring out how to apply them to one's own computing
> needs.

etherwake looks like a slightly more functional package than
wakeonlan, which turns on a computer by addressing its MAC.
My Dell desktops all have that facility, which I use regularly.
You configure it in the BIOS, where the setting sits alongside
the time-triggered configuration.

I used to use time-triggered on one of them, but now that I encrypt
/home, it's not so useful just to boot up at a given time each day.

I assume that nvram-wakeup allows you to choose or change a wakeup
time while the machine is still running. Without it, you'd need
to reboot into the BIOS to set the time, and then switch off.

Unfortunately I've not seen these facilities in any laptop I've used.

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web