[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53580: shepherd's architecture
From: |
Attila Lendvai |
Subject: |
bug#53580: shepherd's architecture |
Date: |
Thu, 08 Jun 2023 20:56:43 +0000 |
> Sorry to be direct: is there a concrete bug you’re reporting here?
i didn't pay careful enough attention to report something specific, but one
thing that pops to mind:
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 my service code is using did not get reloaded into
the PID 1 guile.
keep in mind that this is a non-trivial service that e.g. spawns a long-lived
fiber to talk to the daemon through its stdio while the daemon is running. IOW,
its start GEXP is not just a simple forkexec, but something more complex that
uses functions from guile modules that should be reloaded into PID 1 when the
new version of the service is to be started.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The unexamined life is not worth living for a human being.”
— Socrates (c. 470–399 BC, tried and executed), 'Apology' (399 BC)