Timeline for systemd: Shutdown socket-activated service / disable socket-activation
Current License: CC BY-SA 4.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2019 at 23:38 | answer | added | Graham King | timeline score: 1 | |
| Feb 1, 2019 at 17:56 | comment | added | Michael Hampton | This is not a good use case for socket activation. You should instead configure your web server to drop privileges, like every other web server does. You could also run it on an unprivileged port with a standard web server in front of it, which is possibly a better idea. | |
| Feb 1, 2019 at 17:17 | comment | added | Graham King | root (or capabilities) because it listens on port 443. How would the remote monitoring system talk to systemd? | |
| Feb 1, 2019 at 3:33 | comment | added | Michael Hampton | Why must your service start as root if you don't use socket activation? Why doesn't your monitoring service ask systemd when the service has stopped? | |
| Feb 1, 2019 at 0:34 | history | asked | Graham King | CC BY-SA 4.0 |