kragen 21 hours ago

She credits runit and daemontools as inspiration, and it looks extremely similar. I hope that at some point she writes a comparison explaining what Nitro does differently from runit and why.

Reply View 5 replies
  • cbzbc 19 hours ago

    runit doesn't propagate SIGTERM to services it starts.

    Reply View 4 replies
    • kragen 18 hours ago

      Hmm, is that desirable? If someone's going around sending SIGTERM to random processes they might also send SIGKILL, and there's no way Nitro can propagate SIGKILL to processes it starts.

      Reply View 2 replies
      • cbzbc 10 hours ago

        It does, because SIGTERM is traditionally understood as the trigger for a shutdown. Docker - for instance - will send a SIGTERM to pid 1 when a container is stopped - which goes back to a previous comment here about using a real init as pid 1 if the thing in your container forks: https://news.ycombinator.com/item?id=44990092

        Reply View 1 reply
        • kragen 3 hours ago

          Interesting! I didn't know that—I thought that when you told sysvinit to change its runlevel you normally used some slightly richer interface than signals.

          Reply View 0 replies