-
@ Raito Bezarius
2025-02-15 22:56:38
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqqm3r30r7hfrfd7q7d9aj62vutk522hkhvzvfh0npr242kyqlw8eqn50dca !EHOSTUNREACH could be the actual condition to enable the service, yes, this does not preclude software from implementing proper failure modes for EHOSTUNREACH dynamically but at least, it's not their responsibility to _wait_ for !EHOSTUNREACH and waste my CPU cycles or increase the Restart counter and mess with my ratelimiting of service recovery with systemd
so I do find it useful again, can you walk me how my arguments are insufficient?