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
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 Lars,
Ludovic Courtès skribis:
> Ludovic Courtès skribis:
>
>>> 1 14:12:15.117035 read(21, "(shepherd-command (version 0) (action
>>> restart) (service ssh-daemon) (arguments ()) (directory \"/root\"))", 1024)
>>> = 103
>>> 1 14:12:15.117254 close(27) = 0
>>> 1 14:12:15
Hi,
Attila Lendvai skribis:
> services: Error in MODIFY-SERVICES when services don't exist
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=dbbc7e946131ba257728f1d05b96c4339b7ee88b
>
> one commit prior in the history works fine:
> ae707b62e71b1fae054eb422412384bcc8d39fa9
There were prob
on qemu:
forking-service.sh test always fail.
try use strace but can't:
```
+ /gnu/store/w7a3fxw00y4picvcrkvdxavpj5gqabbb-strace-6.2/bin/strace -f -t -s 80
-o /tmp/she.strace shepherd -I -s t-socket-25862 -c t-conf-25862 -l t-log-25862
--pid=t-pid-25862
+ sleep 0.3
/gnu/store/w7a3fxw00y4picv
the issue:
i'm in a situation where my service quits after a few seconds of CPU usage
(i.e. the default-respawn-limit is not triggered). therefore shepherd keeps
restarting it, practically in a busy loop.
suggested solution:
maybe respawn-service should check for the disabled state, so that th
Guix on a Debian laptop host works okay, GuixSD in VirtualBox a couple
of weeks ago seemed fine too, but I've just spent a weekend trying to
install it on a dedicated laptop for real use, and I'm running into
many problems.
I should split this and file multiple more detailed issues later over
the
Hello,
I may have taken a wrong approach in sending a patch directly to
guix-patc...@gnu.org without posting it here as well, since I noticed
that almost two weeks have passed without responses, whereas huge
traffic of patches and issues were dealt with along the way.
If that mail was indeed over
i forgot to mention that the service is in the stopped state while this is
happening, at least according to `herd status`.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Most of our lives, most of us live in realities determined by others,
imprinted in our brains by education, by relig
