Conversation

Notices

1. Embed this notice
   Poul-Henning Kamp (bsdphk@fosstodon.org)'s status on Thursday, 30-Jan-2025 04:05:29 JST Poul-Henning Kamp

   in reply to

   • Karen Bruner
   • Peter Wemm

   @karinjiri @fuzzykb

   I've always felt it was a mistake that init(8) couldn't take care of this.

   It should read a /etc/programs file and do pretty much exactly what it already does for /etc/ttys

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 30-Jan-2025 04:05:29 JST feld

     in reply to

     • Karen Bruner
     • Peter Wemm
     @bsdphk @karinjiri @fuzzykb whip up this patch you replace like 30% of what people want Systemd for anyway
   • Embed this notice
     Peter Wemm (karinjiri@soc.crashed.org)'s status on Thursday, 30-Jan-2025 04:05:31 JST Peter Wemm

     • Karen Bruner
     I wasn't entirely kidding. Grossly oversimplifying:
     */10 * * * * /path/restartcron
     and restartcron script:
     killall restartcron
     sleep 660 # 11 minutes
     service cron restart
     I used something like it decades ago on AT&T SVR4.0. The cron it came with used the unreliable signal API and occasionally died in the signal race.
     
     Or I could do the proper thing and add some monitoring.