unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36510@debbugs.gnu.org
Subject: bug#36510: confusing mcron logging
Date: Fri, 05 Jul 2019 22:37:57 +0200	[thread overview]
Message-ID: <87r274jjyy.fsf@gnu.org> (raw)
In-Reply-To: <90FD0C85-F140-420C-AD90-3C2776D8B8D0@vllmrt.net> (Robert Vollmert's message of "Fri, 5 Jul 2019 15:35:35 +0200")

Hi,

Robert Vollmert <rob@vllmrt.net> 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 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.

Ludo’.

  reply	other threads:[~2019-07-05 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 13:35 bug#36510: confusing mcron logging Robert Vollmert
2019-07-05 20:37 ` Ludovic Courtès [this message]
2019-07-05 20:48   ` Robert Vollmert
2021-08-18  0:53   ` Maxim Cournoyer
2021-08-24 12:32     ` Maxim Cournoyer
2021-08-30  9:49     ` Ludovic Courtès
2022-01-04 13:21 ` bug#36510: [PATCH v3] base: Annotate output with job information Dale Mellor
2022-11-21  1:22   ` bug#36510: confusing mcron logging Maxim Cournoyer
2022-11-29  3:31     ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r274jjyy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36510@debbugs.gnu.org \
    --cc=rob@vllmrt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).