bug#36510: confusing mcron logging

2022-11-28 Thread Maxim Cournoyer
Hi, Maxim Cournoyer writes: > Dale Mellor writes: [...] >> The output is a little unpredictable. The script (which is >>admittedly somewhat pathological) >> >> (job '(next-second '(0 30)) '(begin (display "test: ") >> (system "date"))) >> >>

bug#36510: confusing mcron logging

2022-11-20 Thread Maxim Cournoyer
Hello Dale, Dale Mellor writes: > Hi, sorry for the delay but I've had a bit of time over Christmas >to look things over. I've given this a lot of consideration. Apologies for my lack of reply thus far, it seems your mail had fallen in cracks. > > I am happy to drop compatibility with guil

bug#36510: confusing mcron logging

2021-08-30 Thread Ludovic Courtès
Hello Maxim, Maxim Cournoyer skribis: > Ludovic Courtès writes: > >> Hi, >> >> Robert Vollmert skribis: >> >>> Suggestions: >>> - mcron should log the timestamp and a job id of every job when it starts >>> - mcron should log the timestamp and status and job id of every job when it >>> finishe

bug#36510: confusing mcron logging

2021-08-24 Thread Maxim Cournoyer
Hello, I sent a v3 of the output annotation patch [0], which no longer blocks reading the output of long-running child processes. I've reconfigured my system with it, so far so good. [0] https://lists.gnu.org/archive/html/bug-mcron/2021-08/msg8.html

bug#36510: confusing mcron logging

2021-08-17 Thread Maxim Cournoyer
Hello Robert and Ludovic, Ludovic Courtès writes: > Hi, > > Robert Vollmert skribis: > >> Suggestions: >> - mcron should log the timestamp and a job id of every job when it starts >> - mcron should log the timestamp and status and job id of every job when it >> finishes >> - job output should

bug#36510: confusing mcron logging

2019-07-05 Thread Robert Vollmert
> On 5. Jul 2019, at 22:37, Ludovic Courtès wrote: > Something that can help debugging to some extent (but is definitely no > substitute for what you suggest above!) is ‘sudo herd schedule mcron’. > I use that to manually run jobs that appear not to work as expected. That only works for non-guile

bug#36510: confusing mcron logging

2019-07-05 Thread Ludovic Courtès
Hi, Robert Vollmert skribis: > Suggestions: > - mcron should log the timestamp and a job id of every job when it starts > - mcron should log the timestamp and status and job id of every job when it > finishes > - job output should be prefixed by some job id +1! +3 even. :-) Something that c

bug#36510: confusing mcron logging

2019-07-05 Thread Robert Vollmert
I have two mcron jobs on my system, certbot renewal and a handwritten and currently buggy guile job. This is an excerpt from /var/log/mcron.log: > Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Cert not yet due for renewal Keep