Hi,
On Wed, 7 May 2014 13:34:29 -0500
Maciej Puzio
On Tue, May 6, 2014 at 3:13 PM, Leonid Isaev
wrote: On Tue, 6 May 2014 13:23:26 -0500 Maciej Puzio
wrote: As I wrote before, I can edit every timer file and set the elapse time. What I can't do is to change one setting which says when daily maintenance tasks are run. This was possible with cron, but is no
You mean, you could change /etc/anacrontab?
longer possible now. What's the problem to edit four files? Well, this is multiplied by the number of machines that are under my care.
Why can't you put additional configs in /etc/systemd/system/xxx.timer.d/ dir?
Again, here is relevant systemd RFE link: https://bugs.freedesktop.org/show_bug.cgi?id=77938
This is bogus.
Leonid, please reread the above paragraph and my previous posts, with comprehension. With all due respect, your replies are not related to the issue discussed.
It is completely unclear what you want to be fixed and the title is misleading... If you have machines m_1 ... m_N and want to spread the anacron jobs, you need to edit N anacrontabs, right? Now you need to do k*N changes, k -- the number of jobs used to be started by anacron. Are you asking for a centralized control affecting all "daily" timers like the per-machine anacrontab? If true, this is unlikely to be implemented (at least I wouldn't do it). Perhaps a proper approach is to create a special target for your maintainance jobs which would pull all relevant services and would itself be triggered by an OnCalendar timer. Although I am not sure whether a timer can directly trigger a target yet... Cheers, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D