4 ms·
runit doesn't propagate SIGTERM to services it starts.
by cbzbc 1y ago
runit doesn't propagate SIGTERM to services it starts.
- kragen 1y agoHmm, 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.
- cbzbc 1y agoIt 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 https://news.ycombinator.com/item?id=44990092
- kragen 1y agoInteresting! 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.
- atahanacar 1y agoIt does if you use SIGHUP.