Sep 22, 2026, 10:51 PMthe wireguard service i've configured in #guix is not working because it always tries to start before my laptop is connected to the internet and fails to resolve hostnames. anyone know how i can make it wait until there is actual connectivity before trying? also how to make the service retry on failure at all?
it's already dependent on the networking service but that's apparently not enough. NetworkManager is generally what gets me online if it matters.
@tmw take a look at this section of the Guix manual:
https://guix.gnu.org/manual/1.5.0/en/html_node/Shepherd-Services.html
You can probably work around your issue by adjusting `respawn-limit` and `respawn-delay`.
Sep 23, 2026, 12:45 PM@shepherd thanks! do you know if there is a common idiom for changing such properties of services created by e.g
(service wireguard-service-type) that are extensions of a shepherd service and don't necessarily accept those parameters directly? (maybe wireguard does accept them, i haven't checked, but my way of doing this kind of thing so far has been hacky and used mutation)
@tmw unfortunately if the Guix service doesn't expose the field of the shepherd service, there is no way to set it. What you can do though, is to create a new Guix service which inherits from the wiregard one but sets its own shepherd service as you see fit.
It's the only way I know, and it's quite hacky.