Thanks for the response. Yes the server program need not bind and listen because systemd socket will do that. On “Accept=True” parameter, here the requirement is that systemd should accept the connection and handover it to server.
My query was on post the connection accept by systemd.
Once the regular connection is accepted, client does SSL_connect over same fd to establish SSL connection. Will this SSL connect request also be handled by systemd ?
Regards, Hari. From: Mantas Mikulėnas [mailto:grawity@xxxxxxxxx]
On Tue, Jan 28, 2020 at 4:23 PM Tiwari, Hari Sahaya <hari-sahaya.tiwari@xxxxxxx> wrote:
You need to remove this part if you want to use socket activation. The whole point of .socket units here is that systemd binds to the socket and passes the fd over to your service. If your service ignores the received fd and tries to create
its own socket, it will never be able to receive the connections. By default, the service would receive the sockets as fd#3 and ahove (see https://www.freedesktop.org/software/systemd/man/sd_listen_fds.html for
documentation), but because you use StandardInput=socket, it will receive the socket as fd#1.
Your .socket specifies Accept=true, so you should remove this part as well: the option means that systemd itself will accept the connection and only hand your server the accepted socket.
-- Mantas Mikulėnas |
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel