[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Taler] Systemd and logging

From: Sebastian Javier Marchano
Subject: Re: [Taler] Systemd and logging
Date: Wed, 13 Apr 2022 13:31:46 -0300

Hi Samuel, MS

I did some research, let me know your comments.


On Tue, 12 Apr 2022 at 16:01, Christian Grothoff <grothoff@gnunet.org> wrote:
Hi Samuel,

MS is right for our deployment-scripts. However, if you take the Debian
packages we produce, there we _do_ already log to journalctl. So the
software can do both -- and the default is stderr-logging.

Sebastian said he'd look into managing the services with a slice

Happy hacking!


On 3/27/22 21:51, ms wrote:
> Hi Samuel,
> On 3/27/22 4:42 PM, Samuel Jahnke wrote:
>> Furthermore, if services logged to stdout, it would be superior in my
>> opinion managing them with journalctl rather than log files.
> This way, if something unobvious goes wrong during the 'prepare'
> step, you are required to search in *two* different places to find the
> logs: the log files folder - where the logs from command line utilities
> get saved - and journalctl for the services.
>> Again, awesome project!
> Thank you!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]