[PATCH] doc: Give references and examples for services-to-restart.

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Simon Josefsson
Owner
unassigned
Submitted by
Simon Josefsson
Severity
normal
S
S
Simon Josefsson wrote on 1 Dec 2020 10:14
(address . bug-guix@gnu.org)
871rg9dh17.fsf@latte.josefsson.org
Hi! I started using unattended-upgrades, and was confused which service
names (config.scm vs herd) to use. I think this small documentation
patch would help others. What do you think?

/Simon
From c414dd60652ecdd124b189b2c46ce30ae9db986d Mon Sep 17 00:00:00 2001
From: Simon Josefsson <simon@josefsson.org>
Date: Tue, 1 Dec 2020 10:10:17 +0100
Subject: [PATCH] doc: Give references and examples for services-to-restart.

* doc/guix.texi (Unattended Upgrades): Give references and examples
for services-to-restart.
---
doc/guix.texi | 4 ++++
1 file changed, 4 insertions(+)

Toggle diff (17 lines)
diff --git a/doc/guix.texi b/doc/guix.texi
index 889f380108..02d3077983 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -17175,6 +17175,10 @@ only restarts services that are not currently running, which is
conservative: it minimizes disruption but leaves outdated services
running.
+Use @command{herd status} to find out candidates for restarting.
+@xref{Services}, for general information about services. Common
+services to restart would include @code{ntpd} and @code{ssh-daemon}.
+
By default, the @code{mcron} service is restarted. This ensures that
the latest version of the unattended upgrade job will be used next time.
--
2.20.1
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSjzJyHC50xCrrUzy9RcisI/kdFogUCX8YJhAAKCRBRcisI/kdF
osoVAPwL7RVR8c/LBEO+HeF9D2UzBLrCk/7jFzYUCBdv3OH0fwEAjHX31SHWJgnI
HHNFq5EvSaYpFsyeOtgoRtZbi6BjFAQ=
=Jw1I
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 3 Dec 2020 17:48
(name . Simon Josefsson)(address . simon@josefsson.org)(address . 44986-done@debbugs.gnu.org)
87wnxydee8.fsf@gnu.org
Hi Simon,

Simon Josefsson <simon@josefsson.org> skribis:

Toggle quote (4 lines)
> Hi! I started using unattended-upgrades, and was confused which service
> names (config.scm vs herd) to use. I think this small documentation
> patch would help others. What do you think?

Sounds like a good idea.

Toggle quote (23 lines)
> From c414dd60652ecdd124b189b2c46ce30ae9db986d Mon Sep 17 00:00:00 2001
> From: Simon Josefsson <simon@josefsson.org>
> Date: Tue, 1 Dec 2020 10:10:17 +0100
> Subject: [PATCH] doc: Give references and examples for services-to-restart.
>
> * doc/guix.texi (Unattended Upgrades): Give references and examples
> for services-to-restart.
> ---
> doc/guix.texi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 889f380108..02d3077983 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -17175,6 +17175,10 @@ only restarts services that are not currently running, which is
> conservative: it minimizes disruption but leaves outdated services
> running.
>
> +Use @command{herd status} to find out candidates for restarting.
> +@xref{Services}, for general information about services. Common
> +services to restart would include @code{ntpd} and @code{ssh-daemon}.

Applied, thanks!

Another option is to look at the ‘shepherdnames’ field in ‘guix system
search’. Not sure if it’s worth mentioning here.

Ludo’.
Closed
?