[Bug 1582015] [NEW] Moving the daily apt timeout after the APT::Periodic::Enable check
Sworddragon
1582015 at bugs.launchpad.net
Sun May 15 19:53:17 UTC 2016
Public bug reported:
I'm using Ubuntu 16.10 dev with apt 1.3~exp1 and I'm noticing that
/etc/cron.daily/apt-compat does set the random timeout and keeping the
related processes that time open before the check for
APT::Periodic::Enable is done in /usr/lib/apt/apt.systemd.daily. Since
the timeout exists to prevent all the users to stress the servers at the
same time but an user might have disabled the periodic job with
APT::Periodic::Enable I think it would be better if setting the timeout
would be moved from /etc/cron.daily/apt-compat to
/usr/lib/apt/apt.systemd.daily at a suitable place somewhere after the
APT::Periodic::Enable check.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1582015
Title:
Moving the daily apt timeout after the APT::Periodic::Enable check
Status in apt package in Ubuntu:
New
Bug description:
I'm using Ubuntu 16.10 dev with apt 1.3~exp1 and I'm noticing that
/etc/cron.daily/apt-compat does set the random timeout and keeping the
related processes that time open before the check for
APT::Periodic::Enable is done in /usr/lib/apt/apt.systemd.daily. Since
the timeout exists to prevent all the users to stress the servers at
the same time but an user might have disabled the periodic job with
APT::Periodic::Enable I think it would be better if setting the
timeout would be moved from /etc/cron.daily/apt-compat to
/usr/lib/apt/apt.systemd.daily at a suitable place somewhere after the
APT::Periodic::Enable check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1582015/+subscriptions
More information about the foundations-bugs
mailing list