On Tue, 15 Oct 2024, Colin Watson wrote: > Looks like this comes from upstream. I agree network-online.target > isn't necessary for the default and common case where you're just > listening on 127.0.0.1. I think using network.target would be a problem > if you set a different listen address in yubihsm-connector.yaml, though; > Go doesn't seem to do IP_FREEBIND.
Right. It might not be a good idea to change that in that case. I wonder if I just misdiagnosed the issue... because I don't see why gdm would have to wait for yubihsm-connector.service to start. At least not more specifically than nginx.service that I also run. I had no delay after removing it but maybe it's just that NetworkManager is behaving differently again after the last upgrade, or some slight difference in my networking environment (I do have an external dock that provides an ethernet interface that seems to have some issues from time to time). > address? And either way, I don't think I see a justification for > Wants=systemd-networkd-wait-online.service - that unit has > Before=network-online.target, so specifying it explicitly seems > redundant. Ack. Cheers, -- Raphaël Hertzog ◈ Freexian SARL ◈ Tel: +33 (0)6 88 21 35 47 https://www.freexian.com
