Hi Simon,
Simon Josefsson <si...@josefsson.org> skribis:
> 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.
> From c414dd60652ecdd124b189b2c46ce30ae9db986d Mon Sep 17 00:00:00 2001
> From: Simon Josefsson <si...@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’.
