4 ms·
> Given that it comes with issues, I assume the benefits outweigh the downsides. Any change can introduce regressions or break habits. The move toward socket a
by idoubtit 1y ago
> Given that it comes with issues, I assume the benefits outweigh the downsides.
Any change can introduce regressions or break habits. The move toward socket activation for sshd is part of a larger change in Debian. I don't think the Debian maintainers changed that just for the fun of it. I can think of two benefits:
+ A service can restart without interruption, since the socket will buffer the requests during the restart.
+ Dependencies are simpler and faster (waiting for a service to start and accept requests is costly).
My experience is that these points largely outweigh the downsides (the only one I can think of is that the socket could be written in two places).
- blueflow 1y ago> Dependencies are simpler and faster (waiting for a service to start and accept requests is costly) Yeah, but requiring a service's response is why its a dependency in the first place, no?
- zbentley 1y agoI also have a hunch that socket activation allows for more predictability around what a not-running/listening-for-activation service's port is doing at the syscall/kernel level, which in turn makes power saving and/or sleep states a little more predictably efficient. Total guess, mind you.