[arch-general] Many timers now running at boot. How to make them run later?

After not booting an Arch box for several days, the first few minutes seem quite MS like lately with a flurry of processes running to the point after I enter my username at the console, it may be 10-20 sec before the password prompt is displayed. Since it's all timers now and not cron running

Re: [arch-general] Many timers now running at boot. How to make them run later?

Hi David, > What is the best way to modify this scheme to prevent, e.g. > logrotate.time, man-db.timer and shadow.timer all trying to run on > boot? I'd rather set them up to run a 5:00 localtime as I would with > cronnie. But I do want to use the systemd timer, so what is the best > way to conf

Re: [arch-general] Many timers now running at boot. How to make them run later?

"David C. Rankin" on Thu, 2019/11/21 04:08: > [...] > > What is the best way to modify this scheme to prevent, e.g. > logrotate.time, man-db.timer and shadow.timer all trying to run on boot? > I'd rather set them up to run a 5:00 localtime as I would with cronnie. But > I do want to use the syst

Re: [arch-general] Many timers now running at boot. How to make them run later?

On 11/21/2019 05:53 AM, Christian Hesse wrote: > I've created systemd configuration overlay snippets for this, for example > /etc/systemd/system/man-db.timer.d/RandomizedDelaySec.conf: > > [Timer] > RandomizedDelaySec=30min > > Create a file for every timer you want to delay. Thank you Ralph & C

[arch-general] Disable pam_securetty.so

Hi, I don't want to come across as impatient but I was wondering how I can accelerate handling of this particular issue: https://bugs.archlinux.org/task/45903?project=1&string=pam I've listed examples in the issue that pam_securetty has been disabled on other major distros. The main issue is tha

Re: [arch-general] Many timers now running at boot. How to make them run later?

"David C. Rankin" on Thu, 2019/11/21 12:13: > I wonder why systemd doesn't do this by default? It's not systemd to blame. The timer unit files are shipped by the respective projects, like util-linux, man-db, mlocate, shadow, logrotate, ... -- main(a){char*c=/*Schoene Gruesse

Re: [arch-general] Disable pam_securetty.so

On Thu, Nov 21, 2019 at 07:35:56PM +0100, Daan De Meyer via arch-general wrote: > Hi, > > I don't want to come across as impatient but I was wondering how I can > accelerate handling of this particular issue: > > https://bugs.archlinux.org/task/45903?project=1&string=pam > > I've listed examples

Re: [arch-general] Many timers now running at boot. How to make them run later?

On Thu, 21 Nov 2019 at 18:13, David C. Rankin wrote: > > On 11/21/2019 05:53 AM, Christian Hesse wrote: > > I've created systemd configuration overlay snippets for this, for example > > /etc/systemd/system/man-db.timer.d/RandomizedDelaySec.conf: > > > > [Timer] > > RandomizedDelaySec=30min > > > >

Re: [arch-general] Many timers now running at boot. How to make them run later?

On Thu, 21 Nov 2019 at 21:02, NTS wrote: > On Thu, 21 Nov 2019 at 18:13, David C. Rankin > wrote: > > > > On 11/21/2019 05:53 AM, Christian Hesse wrote: > > > I've created systemd configuration overlay snippets for this, for > example > > > /etc/systemd/system/man-db.timer.d/RandomizedDelaySec.c

Re: [arch-general] Many timers now running at boot. How to make them run later?

On Thu, 21 Nov 2019 21:36:36 +0100 Maarten de Vries via arch-general wrote: > > Can't you make these services depend on another one which you write to > > start a certain number of minutes after boot? > > > You could, but if you're going to modify the services anyway, then a > randomized del

Re: [arch-general] Many timers now running at boot. How to make them run later?

On 11/21/2019 01:01 PM, Christian Hesse wrote: > "David C. Rankin" on Thu, 2019/11/21 12:13: >> I wonder why systemd doesn't do this by default? > > It's not systemd to blame. The timer unit files are shipped by the respective > projects, like util-linux, man-db, mlocate, shadow, logrotate, ... >