Quote from: tesla80 on April 01, 2025, 10:30:16 PM

Quote from: mcdouglasx on April 01, 2025, 10:14:22 PM

While you are correct in what you say, it is worth noting that this is designed for specific applications, which limits its applicability. Furthermore, if someone knows how to handle systemd, they can replicate some features of Process Watchdog. In the end, whether it is better or not depends on the situation and how the bot to be used is implemented, as it is not an integral solution.

In terms of process management, there is no case that systemd can handle but processWatchdog cannot. It is not for specific applications, it does not limit its applicability at all.
You can use systemd to restart crashing applications and you do not get any stats on it. Process Watchdog mainly focuses on keeping processes alive.
systemd is always an option of course and it was there for ages, it is harder to configure and use.

It is true that PW is simpler and more straightforward in its purpose, but stating that it does not limit applicability at all is debatable, as it depends on the specific needs of the user. systemd excels in managing service dependencies, enabling the configuration of timers, sockets, startup targets, and more. The robustness of systemd makes it preferable when the environment demands advanced functionalities and can also be configured to obtain statistics about bots with tools like journalctl, Prometheus, and Nagios. What I’m trying to convey is that depending on the requirements, one can be equally useful or a better choice than the other. It’s like saying Python is better than C++ just because it’s easier to use.