Hello,
On Sun, Jun 12, 2022 at 11:56:26PM +0100, Štěpán Košan wrote:
> really sorry to bother with a stupid question, however I was wondering, I
> got a warning that CRON is about to be removed in the upgrade, but it seems
> it's still on. Is there a plan to remove it eventually?
I have not seen
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 repla
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
--
htt
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 he
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
Ma
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 th
> 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 mak
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
> NOW=$(
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 det
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 b
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 sy
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 a
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) possible
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 time
Thanks Reco,
I don't know how you keep up after all these years seen you here on the
debian list.
Congrats.
Beco.
On Tue, 15 Sep 2020 at 11:36, Reco wrote:
> Hi.
>
> On Tue, Sep 15, 2020 at 11:19:39AM -0300, Beco wrote:
> > Is this pam module deprecated?
>
> Yes, it was removed fr
Hi.
On Tue, Sep 15, 2020 at 11:19:39AM -0300, Beco wrote:
> Is this pam module deprecated?
Yes, it was removed from main archive back in 2018 - [1].
> I can't find the package that provides it on
> debian buster.
There's no package in buster that provides the PAM module or ConsoleKit
it
On Sun 17 May 2020 at 19:14:46 (-0600), ghe wrote:
> On Sunday, May 17, 2020 4:48 PM, David Wright
> wrote:
>
> > OK, I thought you might list both. I'm not actually sure where output
> > goes because I always have MAILTO set, which takes care of it.
>
> Since I don't know what MAILTO is, I sus
On Sun, May 17, 2020 at 11:21:11AM -0600, ghe wrote:
> > Cron jobs (some of them) don't show up in root's email.
Which MTA are you using, and how did you configure its behavior for
mail addressed to "root"?
Some MTAs will deliver literally to root's inbox (/var/mail/root or
some other place). Ot
On Du, 17 mai 20, 19:14:46, ghe wrote:
>
> Is MAILTO an environmental var? There's no MAILTO in 'env' when root or
> backup (the amanda user) or ghe (me). There's a MAIL in the users'
> environments, but I don't think that's what you're talking about. It's
> pointed at /var/mail/ anyway.
See man
‐‐‐ Original Message ‐‐‐
On Sunday, May 17, 2020 4:48 PM, David Wright
wrote:
> OK, I thought you might list both. I'm not actually sure where output
> goes because I always have MAILTO set, which takes care of it.
Since I don't know what MAILTO is, I suspect I've never had to have it
On Sun 17 May 2020 at 13:05:39 (-0600), ghe wrote:
> On Sunday, May 17, 2020 12:03 PM, David Wright
> wrote:
>
> > I always examine my cron with
> >
> > crontab -l
> >
> > rather than just catting some random file.
>
> Here it is, but I see no difference, except the disabled tripwire.
>
> root
‐‐‐ Original Message ‐‐‐
On Sunday, May 17, 2020 12:03 PM, David Wright
wrote:
> I always examine my cron with
>
> crontab -l
>
> rather than just catting some random file.
>
> Cheers,
> David.
Here it is, but I see no difference, except the disabled tripwire.
root@sbox:~# crontab
On Sun 17 May 2020 at 11:21:11 (-0600), ghe wrote:
> On 5/17/20 10:42 AM, ghe wrote:
> > Buster, Supermicro desktop
> >
> > Cron jobs (some of them) don't show up in root's email.
> >
> > I admin 2 domains -- one on Squeeze, one on Buster. My Squeeze
> > cron results show up fine; Buster's don't.
On 5/17/20 10:42 AM, ghe wrote:
Buster, Supermicro desktop
Cron jobs (some of them) don't show up in root's email.
I admin 2 domains -- one on Squeeze, one on Buster. My Squeeze cron
results show up fine; Buster's don't. I've reinstalled the Buster jobs.
I've copyNpasted them from the Squeeze
On Sun 02 Feb 2020 at 17:32:59 (+1100), Keith Bainbridge wrote:
> On 2/2/20 5:22 am, songbird wrote:
> >it looks questionable to me just in that you
> > may be writing to that file at the same time as
> > you when you're doing something else that is also
> > trying to write to that file.
[…]
On 2/2/20 5:22 am, songbird wrote:
it looks questionable to me just in that you
may be writing to that file at the same time as
you when you're doing something else that is also
trying to write to that file.
Thankyou Songbird and Roberto.
The solution was to escape the % signs in crontab (
Keith Bainbridge wrote:
> Good evening All
>
> I have a niggling problem.Any suggestions, please?
>
> If I run
> echo `date +%d%b%Y` >> /home/keith/.bash_history
> in a xterm (Mate I think always), I get the expected result: a line in
> .bash_history reads
>
> 2020Feb01
> followed by
> echo `dat
On Sat, Feb 01, 2020 at 09:42:25PM +1100, Keith Bainbridge wrote:
> Good evening All
>
> I have a niggling problem.Any suggestions, please?
>
> If I run
> echo `date +%d%b%Y` >> /home/keith/.bash_history
> in a xterm (Mate I think always), I get the expected result: a line in
> .bash_history re
On 1/2/20 10:10 pm, Teemu Likonen wrote:
If you don't want this % effect you need to escape those characters with
backslash:
echo `date +\%Y\%b\%d`
Thankyou
Worked just as I wanted.
--
Keith Bainbridge
keith.bainbridge.3...@gmail.com
0447 667 468
Keith Bainbridge [2020-02-01T21:42:25+11] wrote:
> echo `date +%Y%b%d` >> /home/keith/.bash_history
> I have this line as a cron-job, and constantly get error messages:
>
> /bin/bash: -c: line 0: unexpected EOF while looking for matching ``'
> /bin/bash: -c: line 1: syntax error: unexpected end
Hi.
On Sat, Feb 01, 2020 at 09:42:25PM +1100, Keith Bainbridge wrote:
> I have this line as a cron-job, and constantly get error messages:
>
> /bin/bash: -c: line 0: unexpected EOF while looking for matching ``'
> /bin/bash: -c: line 1: syntax error: unexpected end of file
>
> and no ou
On 17/06/16 04:01, Wim Bertels wrote:
> Hallo,
Hello, Win.
> use case: use cron to mount a sshfs share (with automatic key auth)
>
> on 1 installation this is working fine:
> script:
> "
> #!/bin/bash
>
> sudo -u user1 sshfs user1@123.234.1.2:/var/user1/shared /mnt/shared
>
> exit
> "
>
>
> >
> > on the other it keeps failing because the passphrase needs to be entered
> > to unlock the key, it doesn't fail however without sudo and a custom
> > user1 crontab entry; but as cron is run by root, this should be able to
> > do easier
> >
> > suggestions?
>
> "Install 1" may be using some
Wim Bertels wrote:
> use case: use cron to mount a sshfs share (with automatic key auth)
>
> on 1 installation this is working fine:
> [snipped the script]
>
> on the other it keeps failing because the passphrase needs to be entered
> to unlock the key, it doesn't fail however without sudo and a cu
Quoting Haines Brown (hai...@histomat.net):
> On Sun, Jul 19, 2015 at 10:25:38PM -0500, David Wright wrote:
> > Quoting Haines Brown (hai...@histomat.net):
> >
> > > But I did enable a cron log, which for some reason was disabled on my
> > > system. I'll have to wait a week to see what that log ha
On Sun, Jul 19, 2015 at 10:25:38PM -0500, David Wright wrote:
> Quoting Haines Brown (hai...@histomat.net):
>
> > But I did enable a cron log, which for some reason was disabled on my
> > system. I'll have to wait a week to see what that log has to say. I
> > don't know how to set its level, or if
Quoting Haines Brown (hai...@histomat.net):
> But I did enable a cron log, which for some reason was disabled on my
> system. I'll have to wait a week to see what that log has to say. I
> don't know how to set its level, or if enabling the cron log captures
> all message from the cron daemon.
Wel
Quoting Haines Brown (hai...@histomat.net):
> On Sun, Jul 12, 2015 at 06:33:40PM +, Dan Purgert wrote:
> > Perhaps "environment variable" was the wrong phrase. I've run into
> > issues with cron jobs if I don't have it calling #!/bin/bash at the top
> > (or #!/bin/[whatever]) ... running fro
Haines Brown wrote:
> This may be a FAQ, but it has me stumped. I try to do a weekly backup
> with this, but nothing happens, and there is nothing in syslog:
> # crontab -l
> 0 4 * * 0 /home/haines/scripts/backup
Is this the only line in that crontab?
The default Vixie-cron has the oddity
On Sun, Jul 12, 2015 at 06:33:40PM +, Dan Purgert wrote:
> Perhaps "environment variable" was the wrong phrase. I've run into
> issues with cron jobs if I don't have it calling #!/bin/bash at the top
> (or #!/bin/[whatever]) ... running from a local terminal doesn't catch it
> because "sh s
On Sun, Jul 12, 2015 at 01:37:12PM -0400, Miles Fidelman wrote:
> Dan Purgert wrote:
> It could also be as simple as a permissions issue.
>
> If your syslog isn't showing anything, you might want to push up
> your logging level.
Thanks Miles. I don't know how permissions might come in because the
On Sun, 12 Jul 2015 14:22:22 -0400, Haines Brown wrote:
> On Sun, Jul 12, 2015 at 05:11:21PM +, Dan Purgert wrote:
>> On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
>>
>> > This may be a FAQ, but it has me stumped. I try to do a weekly backup
>> > with this, but nothing happens, and
On Sun, Jul 12, 2015 at 05:11:21PM +, Dan Purgert wrote:
> On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
>
> > This may be a FAQ, but it has me stumped. I try to do a weekly backup
> > with this, but nothing happens, and there is nothing in syslog:
> >
> > # crontab -l 0 4 * * 0 /
Hi
On Sun, 2015-07-12 at 13:02 -0400, Haines Brown wrote:
> This may be a FAQ, but it has me stumped. I try to do a weekly backup
> with this, but nothing happens, and there is nothing in syslog:
>
> # crontab -l
> 0 4 * * 0 /home/haines/scripts/backup
>
> I can run the script manually with
Dan Purgert wrote:
On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
This may be a FAQ, but it has me stumped. I try to do a weekly backup
with this, but nothing happens, and there is nothing in syslog:
# crontab -l 0 4 * * 0 /home/haines/scripts/backup
I can run the script manually
On Sun, 12 Jul 2015 13:02:43 -0400, Haines Brown wrote:
> This may be a FAQ, but it has me stumped. I try to do a weekly backup
> with this, but nothing happens, and there is nothing in syslog:
>
> # crontab -l 0 4 * * 0 /home/haines/scripts/backup
>
> I can run the script manually with # /hom
ML mail wrote:
> Bob Proulx wrote:
> > It is the state of an expired password that is a problem.
> > ...
> > What does this say? Example from a system of mine.
> >
> > $ passwd --status root
> > root P 05/01/2010 0 9 7 -1
> The result of running passwd --status tells me that the password
Hi.
On Fri, 6 Feb 2015 19:39:42 + (UTC)
ML mail wrote:
> So if I understand correctly it is not possible to use cron.d with simply the
> "!" character in the shadow file? I need to have "!" + password? do I
> understand that correctly?
My current configuration is:
# head -1 /etc/shadow
So if I understand correctly it is not possible to use cron.d with simply the
"!" character in the shadow file? I need to have "!" + password? do I
understand that correctly?
On Friday, February 6, 2015 12:24 PM, Reco wrote:
Hi.
On Fri, Feb 06, 2015 at 05:07:58AM -0500, wolf.hal...@gmail.com
Hi.
On Fri, Feb 06, 2015 at 05:07:58AM -0500, wolf.hal...@gmail.com wrote:
> The '!' Means root login is disabled, not that the root account is disabled.
> su -
> With a blank root password lets anyone switch user to root without slowing
> down to crack the password. That is not a safe goal.
The '!' Means root login is disabled, not that the root account is disabled. su
-
With a blank root password lets anyone switch user to root without slowing down
to crack the password. That is not a safe goal.
Sent from my iPhone
> On Feb 6, 2015, at 3:41 AM, ML mail wrote:
>
> The result o
The result of running passwd --status tells me that the password needs to be
changed as actually I had in my /etc/shadow file only a "!" as password in
order to safely disable the root account. It looks like this is not compatible
with the cron.d system. I have changed the password and then lock
ML mail wrote:
> I am trying to run cron from /etc/cron.d with the root account which
> has password disabled in order not to be able to login as root but
> when the cron entry wants to run it simply does not and show the
> following error message in the log file:
>
> CRON[16785]: Authentication t
Don Armstrong writes:
> On Thu, 09 Oct 2014, lee wrote:
>> Tony van der Hoff writes:
>>
>> > GMT/BST; I just want cron to trigger tasks at a fixed time each day,
>> > regardless of localtime.
>>
>> man cron:
>>
>>It is possible to use different time zones for crontables. See
>>
On Thu, 09 Oct 2014, lee wrote:
> Tony van der Hoff writes:
>
> > GMT/BST; I just want cron to trigger tasks at a fixed time each day,
> > regardless of localtime.
>
> man cron:
>
>It is possible to use different time zones for crontables. See
>crontab(5) for more information.
Tony van der Hoff writes:
> GMT/BST; I just want cron to trigger tasks at a fixed time each day,
> regardless of localtime.
man cron:
It is possible to use different time zones for crontables. See
crontab(5) for more information.
man 5 crontab:
The CRON_TZ variable spec
Hi
On Thu, Oct 02, 2014 at 09:20:26PM +0100, Jonathan Dowland wrote:
> On Thu, Oct 02, 2014 at 02:16:06PM -0400, Steve Litt wrote:
> > Thanks Jonathan. I use Docker from time to time, but never knew about
> > LXC. If I use LXC experimentally, what's a good, simple, proof of
> > concept use case?
On Thu, Oct 02, 2014 at 02:16:06PM -0400, Steve Litt wrote:
> Thanks Jonathan. I use Docker from time to time, but never knew about
> LXC. If I use LXC experimentally, what's a good, simple, proof of
> concept use case?
Well it isn't doing anything useful but I created a generic linux guest
using
On Thu, 2 Oct 2014 14:01:34 +0100
Jonathan Dowland wrote:
> On Thu, Oct 02, 2014 at 09:29:35PM +0900, Joel Rees wrote:
> > There's the real problem, and the one that has stopped me in the
> > past -- hardware to set up the dev and test environments. The
> > hardware I have might be able to handle
On Thu, 02 Oct 2014, Jonathan Dowland wrote:
> On Thu, Oct 02, 2014 at 09:29:35PM +0900, Joel Rees wrote:
> > There's the real problem, and the one that has stopped me in the past --
> > hardware to set up the dev and test environments. The hardware I have might
> > be able to handle chroots, but i
On Thu, Oct 02, 2014 at 09:29:35PM +0900, Joel Rees wrote:
> There's the real problem, and the one that has stopped me in the past --
> hardware to set up the dev and test environments. The hardware I have might
> be able to handle chroots, but it won't do VMs. Too old.
LXC is worth a look.
--
2014/10/01 21:29 "Henrique de Moraes Holschuh" :
>
> On Wed, 01 Oct 2014, Joel Rees wrote:
> > Should I use this as my excuse to actually join the dev team, in spite
of
> > my misgivings about systemd and the API creep?
>
> Only if you promisse me you are never going to mention systemd again on
the
On Wed, 01 Oct 2014, Joel Rees wrote:
> Should I use this as my excuse to actually join the dev team, in spite of
> my misgivings about systemd and the API creep?
Only if you promisse me you are never going to mention systemd again on the
communication threads where fcron work is taking place, exc
2014/09/30 21:41 "Henrique de Moraes Holschuh" :
>
> On Tue, 30 Sep 2014, Tony van der Hoff wrote:
> > On 30/09/14 11:57, Henrique de Moraes Holschuh wrote:
> > > On Mon, 29 Sep 2014, Don Armstrong wrote:
> > >> On Mon, 29 Sep 2014, John Hasler wrote:
> > >>> Tony van der Hoff writes:
> > Beli
On Tue, 30 Sep 2014, Tony van der Hoff wrote:
> On 30/09/14 11:57, Henrique de Moraes Holschuh wrote:
> > On Mon, 29 Sep 2014, Don Armstrong wrote:
> >> On Mon, 29 Sep 2014, John Hasler wrote:
> >>> Tony van der Hoff writes:
> Believe me; I've beaten that man to death, but not found the answer
On 30/09/14 11:57, Henrique de Moraes Holschuh wrote:
> On Mon, 29 Sep 2014, Don Armstrong wrote:
>> On Mon, 29 Sep 2014, John Hasler wrote:
>>> Tony van der Hoff writes:
Believe me; I've beaten that man to death, but not found the answer.
Perhaps you'd like to give a more detailed pointe
On Mon, 29 Sep 2014, Don Armstrong wrote:
> On Mon, 29 Sep 2014, John Hasler wrote:
> > Tony van der Hoff writes:
> > > Believe me; I've beaten that man to death, but not found the answer.
> > > Perhaps you'd like to give a more detailed pointer into that manual?
> >
> > See the part about setting
On Mon, 29 Sep 2014, John Hasler wrote:
> Tony van der Hoff writes:
> > Believe me; I've beaten that man to death, but not found the answer.
> > Perhaps you'd like to give a more detailed pointer into that manual?
>
> See the part about setting environment variables. You should be able to
> set T
On Mon, Sep 29, 2014 at 05:13:48PM +0100, Lisi Reisz wrote:
> On Monday 29 September 2014 17:01:31 Tony van der Hoff wrote:
> > well, it's my understanding that the system (hardware) time is always
> > UTC, but there is no way to set localtime to GMT (or UTC). Perhaps I'm
> > misunderstanding you.
On Monday 29 September 2014 17:50:59 Tony van der Hoff wrote:
> I think you do dpkg-reconfigure tzdata, and select Europe/London. There
> is no option for GMT, specifically. Thus you get the twice-yearly hassle
> of DST.
Ah! I configure localtime via my DE (TDE) and get the option of whether I
w
Put your tasks in /etc/crontab and set the system time to UTC. Use each
user's TZ variable to set time zones for them.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
On 29/09/14 17:13, Lisi Reisz wrote:
On Monday 29 September 2014 17:01:31 Tony van der Hoff wrote:
well, it's my understanding that the system (hardware) time is always
UTC, but there is no way to set localtime to GMT (or UTC). Perhaps I'm
misunderstanding you.
Erm What do you think we w
On 29/09/14 17:29, John Hasler wrote:
> Tony van der Hoff writes:
>> Believe me; I've beaten that man to death, but not found the answer.
>> Perhaps you'd like to give a more detailed pointer into that manual?
>
> See the part about setting environment variables. You should be able to
> set TZ=UT
Tony van der Hoff writes:
> Believe me; I've beaten that man to death, but not found the answer.
> Perhaps you'd like to give a more detailed pointer into that manual?
See the part about setting environment variables. You should be able to
set TZ=UTC .
--
John Hasler
jhas...@newsguy.com
Elmwoo
On 29/09/14 17:30, Don Armstrong wrote:
> On Mon, 29 Sep 2014, Tony van der Hoff wrote:
>>> On Wed, 24 Sep 2014 11:54:57 +0100
>> On 24/09/14 16:01, Don Armstrong wrote:
>>> My #1 suggestion is to have system time be GMT, and every shell/user set
>>> TZ appropriately. That's basically the only sane
On 29/09/14 17:48, John Hasler wrote:
> Tony van der Hoff writes:
>> My problem is that cron works to localtime. I want my cron tasks to be
>> triggered at the same time (UTC) each day, regardless of the current
>> localtime, wherever I may be.
>
> man 5 crontab
>
Believe me; I've beaten that man
On 29/09/14 17:13, Lisi Reisz wrote:
> On Monday 29 September 2014 17:01:31 Tony van der Hoff wrote:
>> well, it's my understanding that the system (hardware) time is always
>> UTC, but there is no way to set localtime to GMT (or UTC). Perhaps I'm
>> misunderstanding you.
>
> Erm What do you
Tony van der Hoff writes:
> My problem is that cron works to localtime. I want my cron tasks to be
> triggered at the same time (UTC) each day, regardless of the current
> localtime, wherever I may be.
man 5 crontab
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email t
Lisi Reisz wrote on 09/29/2014 12:13:48 PM:
> On Monday 29 September 2014 17:01:31 Tony van der Hoff wrote:
> > well, it's my understanding that the system (hardware) time is always
> > UTC, but there is no way to set localtime to GMT (or UTC). Perhaps I'm
> > misunderstanding you.
>
> Erm
On Mon, 29 Sep 2014, Tony van der Hoff wrote:
> > On Wed, 24 Sep 2014 11:54:57 +0100
> On 24/09/14 16:01, Don Armstrong wrote:
> > My #1 suggestion is to have system time be GMT, and every shell/user set
> > TZ appropriately. That's basically the only sane setting, as many time
> > zones do DST (an
On Monday 29 September 2014 17:01:31 Tony van der Hoff wrote:
> well, it's my understanding that the system (hardware) time is always
> UTC, but there is no way to set localtime to GMT (or UTC). Perhaps I'm
> misunderstanding you.
Erm What do you think we who live near Greenwich do???
Lisi
Sorry, sent to steve instead of list by mistake
Original Message
Subject: Re: cron in UTC?
Date: Mon, 29 Sep 2014 16:18:35 +0100
From: Tony van der Hoff
To: Steve Litt
> On Wed, 24 Sep 2014 11:54:57 +0100
> Tony van der Hoff wrote:
>
>> Greetings,
>>
On Wed 24 Sep 2014 at 12:44:47 -0400, Steve Litt wrote:
> Somebody once called something or other "string and bailing wire" or
> some such. Well, that's exactly what my homegrown cron is. But it's
> written in Python, managed by daemontools, so it's pretty easy to
> modify to one's own needs.
>
>
On 2014-09-24, Steve Litt wrote:
>
> Somebody once called something or other "string and bailing wire" or
> some such. Well, that's exactly what my homegrown cron is. But it's
> written in Python, managed by daemontools, so it's pretty easy to
> modify to one's own needs.
>
I believe if you're ba
On Wed, 24 Sep 2014 11:54:57 +0100
Tony van der Hoff wrote:
> Greetings,
>
> I carry my wheezy laptop over various timezones, and my VPS with which
> it communicates is on the Europe/London zone, which uses DST.
>
> The result of this is that cron tasks, which are triggered by
> localtime becom
On Wed, 24 Sep 2014, Tony van der Hoff wrote:
> I carry my wheezy laptop over various timezones, and my VPS with which
> it communicates is on the Europe/London zone, which uses DST.
>
> The result of this is that cron tasks, which are triggered by
> localtime become unsynchronised, and only by ar
On 11/05/2014 13:42, Andrei POPESCU wrote:
On Du, 11 mai 14, 12:07:47, Ron Leach wrote:
/var/spool/cron/crontabs/root indeed contains exactly the error you mention:
# DO NOT EDIT THIS FILE - edit the master and reinstall.
[ ... ]
Filip, the comment suggests that I shouldn't edit this file here
On Du, 11 mai 14, 12:07:47, Ron Leach wrote:
>
> /var/spool/cron/crontabs/root indeed contains exactly the error you mention:
>
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.jE2KHC/crontab installed on Fri Dec 31 08:54:50 2010)
> # (Cron version -- $Id: crontab.c,v
Am Sonntag, 11. Mai 2014, 11:53:30 schrieb Ron Leach:
> On 11/05/2014 10:48, Martin Steigerwald wrote:
> > Look into
> >
> > - /etc/cron.d
> > - crontab -l
> >
> > It would not make much sense, but maybe someone added a call to
> > /etc/cron.hourly there.
>
> server4:/# crontab -l
> # /etc/cront
On Sun, 11 May 2014 12:07:47 +0100
Ron Leach wrote:
>
> Filip, the comment suggests that I shouldn't edit this file here. Do
> you have any idea where, or what, its 'master' version might be?
The correct way to edit the per-user crontabs it with
# crontab -u -e
--
To UNSUBSCRIBE, email t
On Du, 11 mai 14, 11:53:30, Ron Leach wrote:
>
> server4:/# crontab -l
> # /etc/crontab: system-wide crontab
I seriously doubt that.
[...]
> How very odd.
> That isn't the content of /etc/crontab .
Since it seems like you executed 'crontab -l' as root is seems like it
is the crontab of the 'r
On 11/05/2014 11:43, Filip wrote:
On Sun, 11 May 2014 10:37:31 +0100
Ron Leach wrote:
I'm missing some aspect of cron configuration, or perhaps some other
cron file somewhere. root doesn't have a /home directory, so there
isn't a crontab in it, and the only user existing on the system
doesn't
On 11/05/2014 10:48, Martin Steigerwald wrote:
Look into
- /etc/cron.d
- crontab -l
It would not make much sense, but maybe someone added a call to
/etc/cron.hourly there.
server4:/# crontab -l
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab
On Sun, 11 May 2014 10:37:31 +0100
Ron Leach wrote:
> I'm missing some aspect of cron configuration, or perhaps some other
> cron file somewhere. root doesn't have a /home directory, so there
> isn't a crontab in it, and the only user existing on the system
> doesn't have a crontab in its hom
On Du, 11 mai 14, 10:37:31, Ron Leach wrote:
>
> I checked /etc/anacrontab in case it could be involved, it seems not to
> contain any cron.hourly entries, nor entries at the relevant time:
>
> SHELL=/bin/sh
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>
> # These replace
1 - 100 of 590 matches
Mail list logo
