diff mbox series

[bug#69302,2/2] doc: Add “Inspecting Services” section.

Message ID 29cc7ff49d15dda51a3c2eb091a4bf603d1f097b.1708527097.git.ludo@gnu.org
State New
Headers show
Series New "Getting Started" section for Guix System | expand

Commit Message

Ludovic Courtès Feb. 21, 2024, 4:47 p.m. UTC
* doc/guix.texi (Inspecting Services): New subsection.

Change-Id: I71378101de913a494e0d0e93cc76434c5a70b520
---
 doc/guix.texi | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)

Comments

pelzflorian (Florian Pelz) Feb. 22, 2024, 5:56 p.m. UTC | #1
Hello Ludo.

Ludovic Courtès <ludo@gnu.org> writes:
> * doc/guix.texi (Inspecting Services): New subsection.

I like this showcasing of useful features.  However, typo:

> +@cindex troubleshooting, for system services
> +@cindex inspecting system services
> +@cindex system services, inspecting
> +As you work on your system configuration, you might wonder why some
> +system service doesn't show up or why the system as not as you expected.

is not as you expected

Also:

> +@example
> +guix system shepherd-graph /etc/config.scm | \
> +  guix shell xdot -- xdot -
> +@end example
> +
> +This lets you visualize the Shepherd services as defined in
> +@file{/etc/config.scm}.  Each box is a service as would be shown by
> +@command{herd status} on the running system, and each arrow denotes a

Perhaps @command{sudo herd status} to avoid confusion?

Regards,
Florian
diff mbox series

Patch

diff --git a/doc/guix.texi b/doc/guix.texi
index e7f59c8bfd..ea2629a768 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -17513,6 +17513,61 @@  Using the Configuration System
   (delete avahi-service-type))
 @end lisp
 
+@unnumberedsubsec Inspecting Services
+
+@cindex troubleshooting, for system services
+@cindex inspecting system services
+@cindex system services, inspecting
+As you work on your system configuration, you might wonder why some
+system service doesn't show up or why the system as not as you expected.
+There are several ways to inspect and troubleshoot problems.
+
+@cindex dependency graph, of Shepherd services
+First, you can inspect the dependency graph of Shepherd services like
+so:
+
+@example
+guix system shepherd-graph /etc/config.scm | \
+  guix shell xdot -- xdot -
+@end example
+
+This lets you visualize the Shepherd services as defined in
+@file{/etc/config.scm}.  Each box is a service as would be shown by
+@command{herd status} on the running system, and each arrow denotes a
+dependency (in the sense that if service @var{A} depends on @var{B},
+then @var{B} must be started before @var{A}).
+
+@cindex extension graph, of services
+Not all ``services'' are Shepherd services though, since Guix System
+uses a broader definition of the term (@pxref{Services}).  To visualize
+system services and their relations at a higher level, run:
+
+@example
+guix system extension-graph /etc/config.scm | \
+  guix shell xdot -- xdot -
+@end example
+
+This lets you view the @dfn{service extension graph}: how services
+``extend'' each other, for instance by contributing to their
+configuration.  @xref{Service Composition}, to understand the meaning of
+this graph.
+
+Last, you may also find it useful to inspect your system configuration
+at the REPL (@pxref{Using Guix Interactively}).  Here is an example
+session:
+
+@example
+$ guix repl
+scheme@@(guix-user)> ,use (gnu)
+scheme@@(guix-user)> (define os (load "config.scm"))
+scheme@@(guix-user)> ,pp (map service-kind (operating-system-services os))
+$1 = (#<service-type localed cabba93>
+      @dots{})
+@end example
+
+@xref{Service Reference}, to learn about the Scheme interface to
+manipulate and inspect services.
+
 @unnumberedsubsec Instantiating the System
 
 @cindex system instantiation