Re: [Taler] Systemd and logging

[Sebastian Javier Marchano]

Hi Samuel, MS

I did some research, let me know your comments.

https://bugs.gnunet.org/view.php?id=7209

--
Sebastian

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
(https://bugs.gnunet.org/view.php?id=7209)

Happy hacking!

Christian

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!