On Du, 06 dec 20, 12:23:43, Martin McCormick wrote:
>
> An on-going problem about self-education is that it's
> easy to limit the scope so much that we miss connections.
> Systemd timers doesn't even sound like a replacement for cron but
> think of it as cron on steroids.
It is also a
Andrei POPESCU writes:
> On Jo, 03 dec 20, 07:39:14, Martin McCormick wrote:
> >
> > So, I need to read more general information about the
> > differences between systemd and what we've been using up to
> > recently.
>
> The Wikipedia page and/or https://systemd.io might be a good place to
On Jo, 03 dec 20, 07:39:14, Martin McCormick wrote:
>
> So, I need to read more general information about the
> differences between systemd and what we've been using up to
> recently.
The Wikipedia page and/or https://systemd.io might be a good place to
start.
Kind regards,
Andrei
--
Hi David,
On Fri, Dec 04, 2020 at 01:32:35PM +1100, David wrote:
> On Fri, 4 Dec 2020 at 13:10, Andy Smith wrote:
> > So much text written without clear statement of problem!
>
> I understand why you wrote that, but you might be unaware that
> Martin has previously mentioned on this list that
On Fri, 4 Dec 2020 at 13:10, Andy Smith wrote:
[...]
> I am surprised that just looking up documentation
> on systemd timers doesn't answer that question for you.
[...]
> So much text written without clear statement of problem!
I understand why you wrote that, but you might be unaware that
Hello,
On Thu, Dec 03, 2020 at 07:39:14AM -0600, Martin McCormick wrote:
> I am guilty as charged but haven't yet found the relevant information
> as to how systemd helps solve this issue.
You can put a time zone in a systemd timer. I can't see how it can
be stated any simpler than that.
If you
Martin McCormick writes:
> I record a news broadcast from one of the BBC services
> every week day at 17:45 British time. When Europe and North
> America stop or start shifting daylight in Autumn or Spring,
> there's a really good chance of missing some of the broadcasts if
> one doesn't
> On Wed, Dec 02, 2020 at 01:58:45PM +, James B wrote:
> > This might be wrong, but as far as I understand doesn't systemd
> > now have the ability to manage cron jobs (as well as mount points,
> > home folders and other things)?. Is there anything in this newer
> > functionality that might
On Wed, Dec 02, 2020 at 01:17:02PM -0500, Dan Ritter wrote:
> As a name for the utility, I suggest "do-if-time-in" and require
> three parameters:
>
> do-if-time-in timezone time "command"
>
> As an interim fix, though: (and I know Greg's going to fix this)
>
> ---
> #!/bin/bash
> TZ=$1
>
Martin McCormick wrote:
> Greg Wooledge writes:
> > I was vaguely thinking of a similar approach. Set up a job that runs
> > every hour, or across a set of hours that will cover all the possible
> > cases that you care about, in your crontab. Within the job itself,
> > set a TZ variable and
Greg Wooledge writes:
> I was vaguely thinking of a similar approach. Set up a job that runs
> every hour, or across a set of hours that will cover all the possible
> cases that you care about, in your crontab. Within the job itself,
> set a TZ variable and determine the time in that time zone
Apols..I hadn't read the original post, just saw this one from today!
--
James B
portoteache...@fastmail.com
Em Qua, 2 Dez ʼ20, às 16:26, Andy Smith escreveu:
> Hello,
>
> On Wed, Dec 02, 2020 at 01:58:45PM +, James B wrote:
> > This might be wrong, but as far as I understand doesn't
Hello,
On Wed, Dec 02, 2020 at 01:58:45PM +, James B wrote:
> This might be wrong, but as far as I understand doesn't systemd
> now have the ability to manage cron jobs (as well as mount points,
> home folders and other things)?. Is there anything in this newer
> functionality that might make
On Wed, Dec 02, 2020 at 08:53:28AM -0500, Dan Ritter wrote:
> It would not be ridiculous to run a wrapper program out of, e.g.
> cron.hourly, which used an explicitly set TZ as a cue to run
> another job.
I was vaguely thinking of a similar approach. Set up a job that runs
every hour, or across
On 02/12/2020 10:30, Martin McCormick wrote:
> In a recent discussion, someone indicated that there might be a
> way to set individual parts such as accounts on a unix system so
> that cron could use another time zone if needed to kickoff jobs
> on that system based on the time in another country.
This might be wrong, but as far as I understand doesn't systemd now have the
ability to manage cron jobs (as well as mount points, home folders and other
things)?. Is there anything in this newer functionality that might make such a
thing (re the request at the beginning of this thread)
Greg Wooledge wrote:
> On Wed, Dec 02, 2020 at 07:30:22AM -0600, Martin McCormick wrote:
> > In a recent discussion, someone indicated that there might be a
> > way to set individual parts such as accounts on a unix system so
> > that cron could use another time zone if needed to kickoff jobs
> >
On Wed, Dec 02, 2020 at 07:30:22AM -0600, Martin McCormick wrote:
> In a recent discussion, someone indicated that there might be a
> way to set individual parts such as accounts on a unix system so
> that cron could use another time zone if needed to kickoff jobs
> on that system based on the
In a recent discussion, someone indicated that there might be a
way to set individual parts such as accounts on a unix system so
that cron could use another time zone if needed to kickoff jobs
on that system based on the time in another country.
As far as I understand cron, one can set
19 matches
Mail list logo
