On Mo, 10.08.20 20:19, Dave Howorth (syst...@howorth.org.uk) wrote:
> > It kinda makes sense to invoke cronjobs the same way as any other
> > piece of system code in userspace: as a service, so that you can take
> > benefit of deps management, priv handling, logging, sandboxing and so
> > on, so
On Mon, 2020-08-10 at 20:19 +0100, Dave Howorth wrote:
> On Mon, 10 Aug 2020 20:21:51 +0200
> Lennart Poettering wrote:
> > i.e. it unifies how system programs are invoked, and that's a good
> > thing. it turns time-based activation into "just another type of
> > activation".
>
> Most of that
On 8/10/2020 12:19 PM, Dave Howorth wrote:
Most of that has gone over my head so some examples would probably help
me to understand. Perhaps they're in the git logs?
The key word is "activation". Modern systems are event-driven. Events
include hardware plugging in, powering up, another
On Mon, 10 Aug 2020 20:21:51 +0200
Lennart Poettering wrote:
> On So, 09.08.20 15:56, Dave Howorth (syst...@howorth.org.uk) wrote:
>
> > Is there anywhere that explains the rationale for systemd timers?
>
> Probably somewhere in the git logs.
Thanks, Lennart. I'll happily poke through the
On So, 09.08.20 00:20, Vini Harimoorthy (vini6...@gmail.com) wrote:
> Hi Team,
>
>
> Is there a way to specify the "start date & time" of the timer unit with
> calendar timer ?
>
> For example, the below timer units runs every weekly from the service is
> activated.My requirement is that I need
On So, 09.08.20 15:56, Dave Howorth (syst...@howorth.org.uk) wrote:
> Is there anywhere that explains the rationale for systemd timers?
Probably somewhere in the git logs.
> What's their USP? Why was it necessary to invent the facility?
It kinda makes sense to invoke cronjobs the same way as
On Sun, Aug 09, 2020 at 06:42:36PM +0200, Jérémy ROSEN wrote:
You could create a timer that starts another timer...
Or something like an `at` job:
$ sudo at 'midnight 2021-01-01'
at> systemctl enable myservice.timer
at> systemctl start myservice.timer
at>
job 1 at Fri Jan
You could create a timer that starts another timer...
Le dim. 9 août 2020 à 16:56, Dave Howorth a écrit :
> On Sun, 9 Aug 2020 15:54:55 +0300
> Andrei Borzenkov wrote:
> > 09.08.2020 13:40, Vini Harimoorthy пишет:
> > > In that case, it will run only in Oct,Nov, & Dec. But, I want to
> > >
On Sun, 9 Aug 2020 15:54:55 +0300
Andrei Borzenkov wrote:
> 09.08.2020 13:40, Vini Harimoorthy пишет:
> > In that case, it will run only in Oct,Nov, & Dec. But, I want to
> > run the timer unit weekly after a specific calendar date & time.
> > How to specify if I want to run some task on every 12
09.08.2020 13:40, Vini Harimoorthy пишет:
> In that case, it will run only in Oct,Nov, & Dec. But, I want to run the
> timer unit weekly after a specific calendar date & time.
> How to specify if I want to run some task on every 12 hours after Jan'2021
> (start from future date & time)
>
That's
In that case, it will run only in Oct,Nov, & Dec. But, I want to run the
timer unit weekly after a specific calendar date & time.
How to specify if I want to run some task on every 12 hours after Jan'2021
(start from future date & time)
Are the below requirements possible with a systemd timer ?
On Sun, Aug 9, 2020 at 12:20 AM Vini Harimoorthy wrote:
> Hi Team,
>
>
> Is there a way to specify the "start date & time" of the timer unit with
> calendar timer ?
>
> For example, the below timer units runs every weekly from the service is
> activated.My requirement is that I need to run the
12 matches
Mail list logo
