Systemd can listen for us and hand over the FD upon service start. This makes the service more restartable as requests aren't lost during the downtime. Restarts during sending are still a problem though as I think the sending stream would get interrupted and upon start not resumed.
https://github.com/coreos/go-systemd
https://github.com/coreos/go-systemd/tree/master/examples/activation/httpserver
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | sitter | T5513 neon-sftp-bridge should systemd socket activate | ||
| Resolved | bshah | T4532 jenkins master -> 16.04 | ||
| Resolved | jriddell | T5505 kitchen not cooking drax mounts | ||
| Resolved | sitter | T5506 neon-sftp-bridge cookbook | ||
| Resolved | sitter | T5514 server-common cookbook should enable journald peristance |
it's a normal user unit rather than socket activated currently
.config/systemd/user/neon-sftp-bridge.service
geoip-kde-org has this implemented properly for an example
https://commits.kde.org/sysadmin/neon-sftp-bridge/a1def5560a8aa66e77c08a350caf6ca48e78fb94
seems to be working. should there be problems in the next couple of days this change is probably why ;)