all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Bruno Victal <mirai@makinata.eu>
Cc: 62163@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#62163: Suppress logging shepherd evaluation in mcron.log
Date: Thu, 27 Apr 2023 15:24:12 +0200	[thread overview]
Message-ID: <87bkj9wj9f.fsf@gnu.org> (raw)
In-Reply-To: <87355kinc5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 01 Apr 2023 00:10:34 +0200")

Hi Bruno,

Ludovic Courtès <ludo@gnu.org> skribis:

> Bruno Victal <mirai@makinata.eu> skribis:
>
>> On 2023-03-30 11:22, Ludovic Courtès wrote:
>>> 
>>> You can send messages to the bitbucket with:
>>> 
>>>   (parameterize ((shepherd-message-port (%make-void-port "w0")))
>>>     …)
>>
>> While it does work for expunging them from mcron log, I noticed that
>> these lines are also polluting /var/log/messages and the snippet above
>> doesn't handle that.
>> Is there perhaps something else I'm missing?
>
> Nope, you cannot prevent them from ending up in /var/log/messages; they
> are purposefully logged.

What should we do about this bug?  Am I right that the conclusion is
that ‘my-heartbeat-job’ could send herd/shepherd output to the bit
bucket?  If yes, we can close this bug.

Thanks,
Ludo’.




  reply	other threads:[~2023-04-27 13:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 15:59 bug#62163: Suppress logging shepherd evaluation in mcron.log Bruno Victal
2023-03-24 12:22 ` Maxim Cournoyer
2023-03-28 16:25   ` Ludovic Courtès
2023-03-28 16:32     ` Bruno Victal
2023-03-30 10:22       ` Ludovic Courtès
2023-03-30 11:21         ` Bruno Victal
2023-03-31  2:10           ` Maxim Cournoyer
2023-03-31 12:18           ` Ludovic Courtès
2023-03-31 11:52         ` Bruno Victal
2023-03-31 22:10           ` Ludovic Courtès
2023-04-27 13:24             ` Ludovic Courtès [this message]
2023-04-27 16:12               ` Bruno Victal
2023-04-28  3:52                 ` Maxim Cournoyer
2023-05-03 20:01                 ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=87bkj9wj9f.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=62163@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=mirai@makinata.eu \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.