I don't know if this has been suggested yet, but I run cron on UTC,
which doesn't do daylight saving time. It's an option in cronie to set
the TZ for crontab. I just have to transcode times from local to UTC
when setting up the job.
On Tue, 07 Nov 2017 08:48:22 +, Mick wrote:
> Apologies for prolonging this exhaustive and exhausting thread, but
> what is the Gentoo suggested cron application for a non-24-7 desktop
> these days? I'm still using sys-process/vixie-cron because I guess
> that's what was de rigueur at the tim
On Monday, 6 November 2017 23:11:44 GMT Rich Freeman wrote:
> On Mon, Nov 6, 2017 at 10:45 AM, Ian Zimmerman wrote:
> > On 2017-11-05 17:17, Rich Freeman wrote:
> >> Distros will always have to do integration work, and that is fine.
> >> That is the role of a distro. And sometimes distros have to
On Mon, Nov 6, 2017 at 10:45 AM, Ian Zimmerman wrote:
> On 2017-11-05 17:17, Rich Freeman wrote:
>
>> Distros will always have to do integration work, and that is fine.
>> That is the role of a distro. And sometimes distros have to roll
>> their own tools when they just aren't available. Once up
On 2017-11-05 17:17, Rich Freeman wrote:
> Distros will always have to do integration work, and that is fine.
> That is the role of a distro. And sometimes distros have to roll
> their own tools when they just aren't available. Once upon a time
> service managers fell into that category. Now th
On Sun, Nov 5, 2017 at 4:40 PM, Ian Zimmerman wrote:
> On 2017-11-05 14:22, Rich Freeman wrote:
>
>> Second, my actual objection is more to sticking wrappers around an
>> upstream program just to extend its capabilities, when other software
>> is maintained upstream that already does what you're r
On 2017-11-05 21:40, Alan McKinnon wrote:
> Agreed again. My desktop cronjobs are all empty and when I had some
> they were of the "do this once a week or once a day" variety. I didn't
> care when they ran, just that they did every so often
What about the synchronization and predictability aspect
On 2017-11-05 14:22, Rich Freeman wrote:
> Second, my actual objection is more to sticking wrappers around an
> upstream program just to extend its capabilities, when other software
> is maintained upstream that already does what you're re-inventing.
> When you already have 47 different cron imple
On 05/11/2017 17:11, Rich Freeman wrote:
> On Sun, Nov 5, 2017 at 6:43 AM, Alan McKinnon wrote:
>>
>> There are other schedulers out there that succeed where cron fails (eg
>> Control-M, chronos, quartz), but those are all large, bulky, designed
>> for big complex installs/requirements and probabl
On Sun, Nov 5, 2017 at 8:10 AM, Ian Zimmerman wrote:
> On 2017-11-05 07:11, Rich Freeman wrote:
>
>> But, I agree that it makes far more sense to just have desktop users
>> use an appropriate cron implementation designed to handle the machine
>> being off most of the time vs trying to use shell sc
On 2017-11-05 18:12, Neil Bothwick wrote:
On Sun, 05 Nov 2017 17:56:56 +0100, Kai Peter wrote:
OT: Seems that since the last update of my MUA the formatting of my
mails is broken - at least at reply's. There are extra line breaks.
G - if you not do everything by yourse
On Sun, 05 Nov 2017 17:56:56 +0100, Kai Peter wrote:
> OT: Seems that since the last update of my MUA the formatting of my
>
> mails is broken - at least at reply's. There are extra line breaks.
>
> G - if you not do everything by yourself ... ;-)
... at least you have someone else to b
There are other schedulers out there that succeed where cron fails (eg
Control-M, chronos, quartz), but those are all large, bulky, designed
for big complex installs/requirements and probably not suited for
simple
things you'd deploy out of a base in portage
Long time ag
On 2017-11-05 07:11, Rich Freeman wrote:
> But, I agree that it makes far more sense to just have desktop users
> use an appropriate cron implementation designed to handle the machine
> being off most of the time vs trying to use shell scripting to make
> vixie cron into such an implementation.
>
On Sun, Nov 5, 2017 at 6:43 AM, Alan McKinnon wrote:
>
> There are other schedulers out there that succeed where cron fails (eg
> Control-M, chronos, quartz), but those are all large, bulky, designed
> for big complex installs/requirements and probably not suited for simple
> things you'd deploy o
On 05/11/2017 16:28, Kai Peter wrote:
>
>
> On 2017-11-04 18:42, Ian Zimmerman wrote:
>
>> On 2017-11-04 01:39, Kai Peter wrote:
>
>>
>
>>> > If you want to run a monthly job on a host that is not always on, do
>
>>> > you have to pretend it's an hourly job and check in the script
>
>>> > it
On 2017-11-04 18:42, Ian Zimmerman wrote:
On 2017-11-04 01:39, Kai Peter wrote:
> If you want to run a monthly job on a host that is not always on, do
> you have to pretend it's an hourly job and check in the script
> itself?
This is a special case to me. IMHO special cases
On 2017-11-04 01:39, Kai Peter wrote:
> > If you want to run a monthly job on a host that is not always on, do
> > you have to pretend it's an hourly job and check in the script
> > itself?
>
> This is a special case to me. IMHO special cases have to be handled
> special or much better: avoid it.
On 2017-11-03 18:21, Ian Zimmerman wrote:
On 2017-11-03 02:53, Kai Peter wrote:
2. the shell script have to do some checks, e.g. the last run - I did
wrote a small 'include' script for that
Isn't your 'small include script' just another implementation of
run-crons?
No.
On 2017-11-03 02:53, Kai Peter wrote:
> 2. the shell script have to do some checks, e.g. the last run - I did
> wrote a small 'include' script for that
Isn't your 'small include script' just another implementation of run-crons?
If not: how does it handle _missed_ jobs, if at all?
If you want to
On 2017-11-01 13:42, Michael Orlitzky wrote:
> If you build cronie with USE=anacron, I think it also comes with an
> "anacron" executable:
>
> https://github.com/cronie-crond/cronie/blob/master/README.anacron
I see, you're quite right. The flag is off here, probably because I
built it when I wa
On 11/01/2017 12:55 PM, Ian Zimmerman wrote:
>
> I actually run cronie, and AFAICT it has no built-in anacron-like
> offline schedule support
If you build cronie with USE=anacron, I think it also comes with an
"anacron" executable:
https://github.com/cronie-crond/cronie/blob/master/README.anac
On 2017-11-01 10:25, Marc Joliet wrote:
> It's nice that anacron apparently sucks, but what about fcron and
> cronie? I've always wondered why people who need these features don't
> just one of those. Is there any reason not to?
>
> (FTR: I used fcron for several years before migrating to syste
Am Sonntag, 29. Oktober 2017, 18:59:31 CET schrieb Ian Zimmerman:
> On 2017-10-29 09:16, Michael Orlitzky wrote:
> > Do you need something smarter? Install anacron, fcron, cronie, or
> > whatever. But the worst thing we can do is try to mimic those
> > intelligent crons and have it fail to do so ra
On 2017-10-29 09:16, Michael Orlitzky wrote:
> Do you need something smarter? Install anacron, fcron, cronie, or
> whatever. But the worst thing we can do is try to mimic those
> intelligent crons and have it fail to do so randomly. That's still
> your best option, by the way: rewrite your crontab
Michael Orlitzky wrote on 2017-10-29 14:16:
> And then the real issue: no one knows what our cronbase is doing, and it
> does whatever it does all wrong -- but some people are probably relying
> on it. My proposal was to make cronbase stupider, with something like
>
> 9 5 * * * root find /
26 matches
Mail list logo