From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: 61146@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#61146] [PATCH Shepherd] doc: Update user services example for `services already running'.
Date: Sun, 29 Jan 2023 12:27:17 +0100 [thread overview]
Message-ID: <87a6218tt6.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi,
I've been struggling with my home shepherd startup for a while,
wondering what changed, overlooking this new error message in the log.
Shouldn't this change have been mentioned in NEWS? FWIW, this now
faulty example is also shown here
https://guix.gnu.org/eo/blog/2020/gnu-shepherd-user-services/
Anyway, as the change was made quite some time ago I imagine that any
other users will have figured this out by now.
Greetings,
Janneke
[-- Attachment #2: 0001-doc-Update-user-services-example-for-services-alread.patch --]
[-- Type: text/x-patch, Size: 2000 bytes --]
From de09ecb16b547830f0df1efc42c78affaaf9c9c4 Mon Sep 17 00:00:00 2001
From: "Jan (janneke) Nieuwenhuizen" <janneke@gnu.org>
Date: Sun, 29 Jan 2023 12:05:32 +0100
Subject: [PATCH Shepherd] doc: Update user services example for `services
already running'.
The previously suggested example now gives
Services already running, so not daemonizing.
which is fixed by daemonizing right away.
This is a follow-up to commit
3197c1c161d10b7f76771a2943f20fdafc5cc14a
service: 'daemonize' action does nothing when services are already running.
* doc/shepherd.texi (Managing User Services): Daemonize before starting
services.
---
doc/shepherd.texi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/shepherd.texi b/doc/shepherd.texi
index d25a8f2..538c334 100644
--- a/doc/shepherd.texi
+++ b/doc/shepherd.texi
@@ -13,7 +13,7 @@ Copyright @copyright{} @value{OLD-YEARS} Wolfgang J@"ahrling@*
Copyright @copyright{} @value{NEW-YEARS} Ludovic Courtès@*
Copyright @copyright{} 2020 Brice Waegeneire@*
Copyright @copyright{} 2020 Oleg Pykhalov
-Copyright @copyright{} 2020 Jan (janneke) Nieuwenhuizen@*
+Copyright @copyright{} 2020, 2023 Jan (janneke) Nieuwenhuizen@*
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -1353,6 +1353,9 @@ load individual service definitions from
(use-modules (shepherd service)
((ice-9 ftw) #:select (scandir)))
+;; Send shepherd into the background
+(action 'shepherd 'daemonize)
+
;; Load all the files in the directory 'init.d' with a suffix '.scm'.
(for-each
(lambda (file)
@@ -1361,8 +1364,6 @@ load individual service definitions from
(lambda (file)
(string-suffix? ".scm" file))))
-;; Send shepherd into the background
-(action 'shepherd 'daemonize)
@end lisp
Then, individual user services can be put in
--
2.38.1
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
next reply other threads:[~2023-01-29 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 11:27 Janneke Nieuwenhuizen [this message]
2023-03-04 19:51 ` bug#61146: [PATCH Shepherd] doc: Update user services example for `services already running' Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6218tt6.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=61146@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).