Bug#964438: apt-listbugs: dns error when running from cron job

Michael Biebl biebl at debian.org
Sun Jul 26 21:06:23 BST 2020


Am 26.07.20 um 21:36 schrieb Francesco Poli:
> Control: reassign -1 systemd
> 
> 
> On Fri, 17 Jul 2020 18:11:08 +0200 Francesco Poli wrote:
> 
>> On Fri, 17 Jul 2020 01:46:06 +0200 Michael Biebl wrote:
> [...]
>>> network-online.target is only relevant during boot, once the target has
>>> been reached, it will stay up, it is not dynamic.
>>> I.e. you can't use that to delay the execution of a service after
>>> suspend-resume.
> [...]
>>>
>>> Reassigning accordingly.
>>
>> Hello Michael, thanks for your prompt reply.
>>
>> OK, I acknowledge that the network-online.target check is not reliable
>> enough, I was aware of that.
>>
>> But anyway, let's pretend the network check is completely absent.
>>
>> Why is the service triggered *immediately* during wake-up?
>> It should wait at least 5 min (OnActiveSec=5min) or be triggered on the
>> basis of the calendar scheduling (OnCalendar=*-*-* *:20) with a random
>> delay (RandomizedDelaySec=20min).
>>
>> And it should *not* catch up with missed execution chances (since the
>> timer is *not* a Persistent=true one).
>>
>> What am I missing here?
> 
> Dear Michael,
> I am still convinced that this is a bug in systemd, as explained above.
> I am reassigning back the bug report to package systemd.
> 
> If you think that the timer unit can be modified so that it behaves as
> intended, please tell me how I should modify it.
> Just to recap the intended behavior: the timer should trigger the
> corresponding oneshot service 5 min after the timer activation and then
> hourly, with a random delay between 0 and 20 min, *without* catching up
> with missed execution chances, and it should *not* trigger the service
> immediately during a wake-up from sleep.

Maybe this is a misunderstanding. Persistent=true is relevant when you
reboot/power down a system. In your case, the system is suspended and
woken up again.

> Otherwise, please investigate/fix the issue and/or forward my
> bug report upstream, as appropriate.

Not sure what I'm supposed to investigate or fix here, sorry. So I can't
forward anything upstream either.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200726/9ad18547/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list