Mantas,
Thanks for pointing out the relationship between “Accept=yes” in the socket
unit and the service unit being a template. I missed that; probably because the
service is started rarely.
Kind regards,
Ulrich
From: Mantas Mikulėnas
Sent: Thursday, December 5, 2024 2:39 PM
To: Windl, Ulrich
On Thu, Dec 5, 2024 at 1:29 PM Windl, Ulrich wrote:
> Hi!
>
>
>
> I wonder: If a socket unit is using an TCP/IP (v4) stream socket, can’t
> systemd deduce that the socket should start **after** the network had
> been set up?
>
It *technically* could watch netlink for that, but likewise you could
Hi!
I wonder: If a socket unit is using an TCP/IP (v4) stream socket, can't systemd
deduce that the socket should start *after* the network had been set up?
Specifically I had the case in SLES15 SP6
(systemd-254.18-150600.4.15.10.x86_64) that this socket unit failed to start
after the paths ta
