Attila Lendvai skribis:
> (define (call-with-server-socket file-name proc)
> "Call PROC, passing it a listening socket at FILE-NAME and deleting the
> socket file at FILE-NAME upon exit of PROC. Return the values of PROC."
> (let ((sock (open-server-socket file-name)))
> (dynamic-wind
>
Hi,
Attila Lendvai skribis:
> when i'm working on my service code, which is `guix pull`ed in from my
> channel, then after a reconfigure i seem to have to reboot for my new code to
> get activated. a simple `herd restart` on the service didn't seem to be
> enough. i.e. the guile modules that
Hello Attila,
I had totally overlooked this bug report.
Attila Lendvai skribis:
> the systems seems to work fine. Gnome is up, i can log in with my user, and
> everything seems to work, except herd.
>
> i encounter this broken state every once in a while. IRC logs also mention
> this
FTR,
the issue is that when Shepherd is booting up, i.e. starting from its config
file, it calls the start forms without guarding for any possible exceptions.
any error propagates up beyond the loop and up until an unwind protect that
deletes the socket.
the reason my system seemed fully
Attila Lendvai schreef op do 27-01-2022 om 11:32 [+]:
> (define (call-with-server-socket file-name proc)
> "Call PROC, passing it a listening socket at FILE-NAME and deleting the
> socket file at FILE-NAME upon exit of PROC. Return the values of PROC."
> (let ((sock (open-server-socket
the systems seems to work fine. Gnome is up, i can log in with my user, and
everything seems to work, except herd.
i encounter this broken state every once in a while. IRC logs also mention this
multiple times, but without many insights:
