On Fr, 05.07.24 16:19, Andrea Pappacoda (and...@pappacoda.it) wrote:
> Hi all!
>
> I'm writing a small FastCGI daemon which, in addition to the socket used
> to talk FastCGI to the web server, talks SMTP through another (inet)
> socket (as an SMTP client).
>
> The FastCGI socket is created by syst
> On 5 Jul 2024, at 15:25, Andrea Pappacoda wrote:
>
> Ideally, I'd just get fd 3 and use it to listen for incoming requests,
> and get fd 4 and use it to talk TLS + SMTP over TCP to the remote (or
> local) SMTP server.
If systemd opens the socket that means that you cannot do retries or repo
A service could receive multiple listeners sockets, but I don't remember
systemd having an option to pass client connection sockets – and I don't
think it would make much sense, as the SMTP server is likely to close the
connection while the service is still running, and then systemd would
definitel
Hi all!
I'm writing a small FastCGI daemon which, in addition to the socket used
to talk FastCGI to the web server, talks SMTP through another (inet)
socket (as an SMTP client).
The FastCGI socket is created by systemd with a .socket unit and passed
to the service as an fd (which also enables soc
