Re: [systemd-devel] multiple starts for a socket-based service

On 06.08.2023 03:42, Ross Boylan wrote: On Fri, Aug 4, 2023 at 4:32 PM Kevin P. Fleming wrote: On Fri, Aug 4, 2023, at 18:11, Ross Boylan wrote: Theory: since br0 has no associated IP address when socket creation is attempted, the socket creation fails. If so, I need to delay socket startup

Re: [systemd-devel] multiple starts for a socket-based service

On Fri, Aug 4, 2023 at 4:32 PM Kevin P. Fleming wrote: > > On Fri, Aug 4, 2023, at 18:11, Ross Boylan wrote: > > Theory: since br0 has no associated IP address when socket creation is > > attempted, the socket creation fails. If so, I need to delay socket > > startup until br0 has an IP4

[systemd-devel] Unit in network namespace uses default namespace resolv.conf instead of the bind mount /etc/netns//resolv.conf

Hello, can someone please help me fix this: https://github.com/systemd/systemd/issues/28694? The transmission-daemon that is started via systemd in a dedicated network namespace is seeing the main namespace resolv.conf instead of the one mounted by netns. If I manually pop into the vpn

Re: [systemd-devel] Conditionally reload a service from another service

> On 31 Jul 2023, at 21:23, Ian Pilcher wrote: > > I have created service (along with an associated timer) that checks the > remaining life of a TLS certificate and retrieves an updated certificate > from Let's Encrypt if the remaining life is too short. Certbot already knows how to do this.