Not all operating systems use systemd, and thus don't necessarily support the systemd watchdog. One example would be macOS 💻. However, with the current setup, an error is issues that the systemd watchdog is unsupported on each start of Poseidon.
When error reporting to Sentry is enabled, consequentially, each start of Poseidon on macOS reports a new event (which I have to delete manually). It would be great if we could change the current behavior.
I see the following potential approaches:
Add a config option to disable the systemd watchdog
Lower the level of the "Systemd Watchdog not supported" error (maybe similar to "Systemd Readiness Notification not supported")
Couple systemd readiness notifications and systemd Watchdog: Return from notifySystemd, when systemd readiness notifications are not supported
Not all operating systems use systemd, and thus don't necessarily support the systemd watchdog. One example would be macOS 💻. However, with the current setup, an error is issues that the systemd watchdog is unsupported on each start of Poseidon.
When error reporting to Sentry is enabled, consequentially, each start of Poseidon on macOS reports a new event (which I have to delete manually). It would be great if we could change the current behavior.
I see the following potential approaches:
notifySystemd
, when systemd readiness notifications are not supported