Hi Ludo’, On 2023-04-27 14:24, Ludovic Courtès wrote: > Hi Bruno, > > Ludovic Courtès <l...@gnu.org> skribis: > >> Bruno Victal <mi...@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.
Perhaps we could have a “low-noise” way to query for running services? (or non modifying actions done on shepherd) Filling /var/log/messages with messages of (IMO) dubious value seems counterproductive. > 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. Parameterizing the shepherd-message-port did cut the shepherd messages from the mcron log, yes. Cheers, Bruno
