Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Tuesday, 01-Aug-2023 23:01:26 JST feld
   Systemd auto-restarts of units can hide problems from you
   
   https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdRestartHidesProblems
   
   
   If your services are crashing, auto-restarting them is not the "fix". This is nice to have, but the system really really really needs to give the end users scary warnings that it should not be happening. There should be an obvious way to trap these events and make them become alerts.
   • narcolepsy and alcoholism :flag: likes this.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Tuesday, 01-Aug-2023 23:35:33 JST feld

     in reply to

     • Pete Wright
     I still use daemontools/runit a lot because it's simpler to run some services with it.
     
     It's been helpful with a few apps that try to incorporate their own shutdown/restart/update capabilities which doesn't work right on FreeBSD (pkg unaware, etc) so if those run by accident the service will just die and auto restart itself
   • Embed this notice
     Pete Wright (pete_wright@nlogic.systems)'s status on Tuesday, 01-Aug-2023 23:35:34 JST Pete Wright

     in reply to
     @feld I blame djb for this anti-pattern. Daemontools was a warning for us, not an blueprint systemd
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Tuesday, 01-Aug-2023 23:37:06 JST feld

     in reply to

     • Pete Wright
     I do think that running in the foreground is better but the supervision needs more monitoring capabilities