Hi,
Tomas Volf <~@wolfsden.cz> skribis:
> I have no idea how Shepherd works internally (and much less how Fibers
> work), so maybe this comment is completely off, but this seems
> suspicious. Should this lambda not get the wake up time as an argument,
> instead of calling get-internal-real-time
Ludovic Courtès writes:
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> (I wonder if there is better way to detect the sleep. I feel like *any*
>> number will be wrong for someone. Do we know how for example systemd's
>> timers handle this?)
>
> I believe systemd is the one initiating hibernation, s
Tomas Volf <~@wolfsden.cz> skribis:
> (I wonder if there is better way to detect the sleep. I feel like *any*
> number will be wrong for someone. Do we know how for example systemd's
> timers handle this?)
I believe systemd is the one initiating hibernation, so it has the
information first-hand
Ludovic Courtès writes:
> Ludovic Courtès skribis:
>
>>> 2025-02-23 12:00:02 Waiting anew for timer 'kerberos-log-in-refresh'
>>> (resuming from sleep state?).
>
> The “Waiting anew” message happens when the timer fires 2 seconds or
> more later than expected (see ‘sleep-operation/check’), whic
Ludovic Courtès writes:
> Hi Tomas,
>
> Tomas Volf <~@wolfsden.cz> skribis:
>
>> However that did not happen. Here are the logs:
>>
>> 2025-02-22 19:17:00 Service kerberos-log-in running with value #<
>> id: 730 command: ("/gnu/store/8m21cnqnllk6g1kcgyj91i5h05s7c0c4-krb-log-in")>.
>> 2025-02-22
Ludovic Courtès skribis:
>> 2025-02-23 12:00:02 Waiting anew for timer 'kerberos-log-in-refresh'
>> (resuming from sleep state?).
The “Waiting anew” message happens when the timer fires 2 seconds or
more later than expected (see ‘sleep-operation/check’), which is indeed
the case here.
It’s not
Hi Tomas,
Tomas Volf <~@wolfsden.cz> skribis:
> However that did not happen. Here are the logs:
>
> 2025-02-22 19:17:00 Service kerberos-log-in running with value #<
> id: 730 command: ("/gnu/store/8m21cnqnllk6g1kcgyj91i5h05s7c0c4-krb-log-in")>.
> 2025-02-22 19:17:00 [8m21cnqnllk6g1kcgyj91i5h05
Hi,
I might have find a bug in shepherd timers. I have a timer scheduled to
run every 24 hours, the definition is as follow:
--8<---cut here---start->8---
(define %kerberos-log-in-refresh-service
(let ((name 'kerberos-log-in-refresh))
(simple-service
