Robert Vollmert skribis:
> One related issue that I just ran into, while trying out the gexp approach:
>
> mcron jobs take an optional third naming argument, which are again better
> not used because they replace the store filename in the “schedule”
> output.
I see; that feature was not
One related issue that I just ran into, while trying out the gexp approach:
mcron jobs take an optional third naming argument, which are again better
not used because they replace the store filename in the “schedule”
output.
Hi,
Robert Vollmert skribis:
>> On 7. Jul 2019, at 16:24, Ludovic Courtès wrote:
>>
>> Hi Robert,
>>
>> Robert Vollmert skribis:
>>
>>> Defined a mcron job in config.scm scheduled to run once a day,
>>> with a scheme expression. How do I test this?
>>>
>>> herd schedule mcron lists the
> On 7. Jul 2019, at 16:24, Ludovic Courtès wrote:
>
> Hi Robert,
>
> Robert Vollmert skribis:
>
>> Defined a mcron job in config.scm scheduled to run once a day,
>> with a scheme expression. How do I test this?
>>
>> herd schedule mcron lists the job as merely a “Lambda expression”.
>> I
Hi Jesse,
Jesse Gibbons skribis:
> mcron is super buggy in my experience. If I power my laptop off
> overnight it will skip all jobs scheduled for the day of the month,
> even if they are scheduled for after I power it back on. And it doesn't
> have a way to easily schedule for a given day of
> My issue:
> Defined a mcron job in config.scm scheduled to run once a day,
> with a scheme expression. How do I test this?
Write the mcron job for a local installation of mcron first for
testing purposes, then move it into config.scm. That's how I do it.
> herd schedule mcron lists the job as
My issue:
Defined a mcron job in config.scm scheduled to run once a day,
with a scheme expression. How do I test this?
herd schedule mcron lists the job as merely a “Lambda expression”.
I learned how to give it a descriptive name, but still there’s
no script linked that I can run by hand.
One
