From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: 35686@debbugs.gnu.org
Subject: [bug#35686] [PATCH] doc: Document 'auto-start?' field of 'shepherd-service'.
Date: Sat, 11 May 2019 18:05:41 +0200 [thread overview]
Message-ID: <875zqh0yei.fsf@GlaDOS.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
Hi Guix,
This patch adds the missing 'auto-start?' field to the documentation of
'shepherd-service'.
I have also noticed that the 'documentation' field is not in the same
position as it is in the source code (the remaining fields are in the
right order). I did not change this as I was not sure whether it was
done on purpose.
Regards,
Diego
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-Document-auto-start-field-of-shepherd-service.patch --]
[-- Type: text/x-patch, Size: 943 bytes --]
From 74c8321303d47b7c28f873c4e560b9fbaf136cfb Mon Sep 17 00:00:00 2001
From: Diego Nicola Barbato <dnbarbato@posteo.de>
Date: Sat, 11 May 2019 17:21:18 +0200
Subject: [PATCH] doc: Document 'auto-start?' field of 'shepherd-service'.
* doc/guix.texi (shepherd-service): Document 'auto-start?' field.
---
doc/guix.texi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 3f50bf77fe..86ed199aed 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -25312,6 +25312,10 @@ This is a list of @code{shepherd-action} objects (see below) defining
herd @var{action} @var{service} [@var{arguments}@dots{}]
@end example
+@item @code{auto-start?} (default: @code{#t})
+Whether this service should be started automatically by the Shepherd. If it
+is @code{#f} the service has to be started manually with @code{herd start}.
+
@item @code{documentation}
A documentation string, as shown when running:
--
2.21.0
next reply other threads:[~2019-05-11 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 16:05 Diego Nicola Barbato [this message]
2019-05-12 21:33 ` bug#35686: [PATCH] doc: Document 'auto-start?' field of 'shepherd-service' 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zqh0yei.fsf@GlaDOS.home \
--to=dnbarbato@posteo.de \
--cc=35686@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.