11 ms·
You can, but it doesn't. If I know I want to start it I can just connect with the client. Sounds like you're arguing something like "yes, it's broken. But you
by knorker 5y ago
You can, but it doesn't. If I know I want to start it I can just connect with the client.
Sounds like you're arguing something like "yes, it's broken. But you can just reimplement everything and it won't be broken anymore".
Yes, I can also turn off "kill user processes on logout", but that doesn't make that not-broken.
- yawaramin 5y agoNo, I'm arguing there's a way to force-start even socket-activated services. But this is really a moot point. Systemd's socket activation is really meant for system services which would otherwise be in the critical path of system boot. 'Regular' client-facing services that people normally run–webapps, etc.–are not really the target use case. It's fine to start them up in the normal way, with WantedBy=multi-user.target in the [Install] section. And I have never seen people use socket activation for them anyway. So you are basically arguing a strawman here.
- knorker 5y ago> So you are basically arguing a strawman here. gpsd is an example that immediately comes to mind that was set to start on-demand. Which is ridiculous. So it's a straw man that actually exists, making it not a straw man.