Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1019404
| From | Francesco Poli <invernomuto@paranoici.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#964438: apt-listbugs: dns error when running from cron job |
| Date | 2020-07-26 23:30 +0200 |
| Message-ID | <AwWnw-5OT-11@gated-at.bofh.it> (permalink) |
| References | (15 earlier) <AwVKO-5m0-13@gated-at.bofh.it> <AwVKO-5m0-9@gated-at.bofh.it> <AwWnw-5OT-13@gated-at.bofh.it> <ApSoG-7UJ-9@gated-at.bofh.it> <AwWnw-5OT-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sun, 26 Jul 2020 22:48:18 +0200 Michael Biebl wrote:
> Am 26.07.20 um 22:43 schrieb Francesco Poli:
> > On Sun, 26 Jul 2020 22:22:55 +0200 Michael Biebl wrote:
> >
> > [...]
> >> Afaics, the problem is, that your service does not properly handle the
> >> case, when the network is not available.
> >
> > It does, that's the reason why the operation is attempted hourly.
>
> The bug report was about apt-listbugs throwing an error if network is
> not available.
We can argue that the service should be more silent in case of network
errors, or maybe it's OK that it throws an error.
But that's not the point.
The point is that the timer triggers during wake-up, while it should
behave as it does during a boot (wait for at least 5 min and then
trigger hourly, with a random delay).
>
> >> Even if systemd would delay timer events after a resume: How long should
> >> it wait? 30s, 1min? How would that robustly solve your problem? How
> >> would that guarantee that after 1min network is available?
> >
> > It should wait at least 5 min (as specified in OnActiveSec=5min),
>
> That is not what OnActiveSec=5min means
Then I think the systemd.timer(5) man page should be clarified.
It states:
│OnActiveSec= │ Defines a timer relative │
│ │ to the moment the timer │
│ │ unit itself is activated. │
I thought this meant that an OnActiveSec=5min timer triggers 5 min
after being activated.
And the timer is either inactive during sleep (then it's activated
again during wake-up and it should wait 5 min before triggering) or
considered as active during sleep (but then the OnActiveSec should have
already happened 5 min after boot and should not happen again during
wake-up).
What did I fail to understand?
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#964438: apt-listbugs: dns error when running from cron job Oswald Buddenhagen <oswald.buddenhagen@gmx.de> - 2020-07-07 11:50 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-07 20:00 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Oswald Buddenhagen <oswald.buddenhagen@gmx.de> - 2020-07-07 20:30 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-07 23:00 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Oswald Buddenhagen <oswald.buddenhagen@gmx.de> - 2020-07-07 23:10 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-13 23:40 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Oswald Buddenhagen <oswald.buddenhagen@gmx.de> - 2020-07-14 10:40 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-14 23:00 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Oswald Buddenhagen <oswald.buddenhagen@gmx.de> - 2020-07-15 11:00 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-16 23:20 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-16 23:50 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-17 18:20 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-26 21:40 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-26 22:50 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-26 22:50 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-26 23:30 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-26 23:30 +0200
Bug#964438: apt-listbugs: dns error when running from cron job Francesco Poli <invernomuto@paranoici.org> - 2020-07-27 23:40 +0200
csiph-web