Your message dated Wed, 22 Jul 2020 18:31:51 +0200 with message-id <20200722182817.GA51420@debian.org> and subject line Re: Bug#965997: APT::Periodic::RandomSleep is ignored on machines running systemd has caused the Debian Bug report #965997, regarding APT::Periodic::RandomSleep is ignored on machines running systemd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 965997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965997 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: APT::Periodic::RandomSleep is ignored on machines running systemd
- From: Louis-Philippe Véronneau <pollo@debian.org>
- Date: Tue, 21 Jul 2020 19:54:28 -0400
- Message-id: <[🔎] 25687f62-78e2-4c90-48d3-f9dbfd5568dd@debian.org>
Package: apt Version: 1.8.2.1 Severity: normal Dear maintainers, Since apt transitioned from a cronjob to a systemd timer, /etc/cron.daily/apt-compat now starts with: if [ -d /run/systemd/system ]; then exit 0 fi Sadly, this cronjob was also the one responsible for parsing APT::Periodic::RandomSleep. The new systemd timer indeed seems to hardcode the RandomizedDelaySec value [1]. Would it be possible to change that behavior and make sure the systemd timer also uses the APT::Periodic::RandomSleep parameter? Thanks, [1] https://salsa.debian.org/apt-team/apt/-/blob/master/debian/apt-daily.timer -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org ⠈⠳⣄Attachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
- To: Louis-Philippe Véronneau <pollo@debian.org>, 965997-done@bugs.debian.org
- Subject: Re: Bug#965997: APT::Periodic::RandomSleep is ignored on machines running systemd
- From: Julian Andres Klode <jak@debian.org>
- Date: Wed, 22 Jul 2020 18:31:51 +0200
- Message-id: <20200722182817.GA51420@debian.org>
- In-reply-to: <[🔎] 25687f62-78e2-4c90-48d3-f9dbfd5568dd@debian.org>
- References: <[🔎] 25687f62-78e2-4c90-48d3-f9dbfd5568dd@debian.org>
On Tue, Jul 21, 2020 at 07:54:28PM -0400, Louis-Philippe Véronneau wrote: > Package: apt > Version: 1.8.2.1 > Severity: normal > > Dear maintainers, > > Since apt transitioned from a cronjob to a systemd timer, > /etc/cron.daily/apt-compat now starts with: > > if [ -d /run/systemd/system ]; then > exit 0 > fi > > Sadly, this cronjob was also the one responsible for parsing > APT::Periodic::RandomSleep. > > The new systemd timer indeed seems to hardcode the RandomizedDelaySec > value [1]. > > Would it be possible to change that behavior and make sure the systemd > timer also uses the APT::Periodic::RandomSleep parameter? No, please configure the timer with a drop-in. Currently the timer runs at a random time throughout the day (it has 24h randomization). There's no plan to provide configurability of any delays or intervals outside of systemd timers. Currently we still honor the options, but they cannot interact correclty with when the timers are launched, and retries on failure. Hence we'll be moving to a world where you do any configuration of timing aspects via systemd timers. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
--- End Message ---