Hi,
"pelzflorian (Florian Pelz)" <[email protected]> skribis:
> On Tue, Apr 14, 2020 at 04:36:12PM +0200, Ludovic Courtès wrote:
>> Could you build an ISO image with the patch below on top of
>> bd4c345ef7ddf3542662fe0872b06393b414a3fc and confirm that it works for
>> you?
>
> Sorry it still fails despite /gnu/store/*shepherd.conf really
> containing the set! of the timeout to 30. I attach /var/log/messages.
Silly me, I think it works if we set! before loading services.
Could you double-check with the patch below?
This is the last thing, and then all the lights are green!
Ludo’.
diff --git a/gnu/services/shepherd.scm b/gnu/services/shepherd.scm
index bad089844d..9906ae43c4 100644
--- a/gnu/services/shepherd.scm
+++ b/gnu/services/shepherd.scm
@@ -291,6 +291,13 @@ and return the resulting '.go' file."
(default-environment-variables
'("PATH=/run/current-system/profile/bin"))
+ ;; Booting off a DVD, especially on a slow machine, can make
+ ;; everything slow. Thus, increase the timeout compared to the
+ ;; default 5s in the Shepherd 0.7.0. See
+ ;; <https://bugs.gnu.org/40572>.
+ ;; XXX: Use something better when the next Shepherd is out.
+ (set! (@@ (shepherd service) %pid-file-timeout) 30)
+
;; Arrange to spawn a REPL if something goes wrong. This is better
;; than a kernel panic.
(call-with-error-handling
