From fcecb23091ead657ee70f273740a5ca7bd09d931 Mon Sep 17 00:00:00 2001 From: Ramkumar Rajagopalan Date: Thu, 4 Oct 2018 19:50:13 +0200 Subject: [PATCH] Fix relative paths for images in processes.asciidoc --- chapters/processes.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/chapters/processes.asciidoc b/chapters/processes.asciidoc index aec6c0a..78ea633 100644 --- a/chapters/processes.asciidoc +++ b/chapters/processes.asciidoc @@ -350,7 +350,7 @@ or from the Erlang shell with: When the Observer is started it will show you a system overview, see the following screen shot: -image::images/observer_system.png[] +image::../images/observer_system.png[] We will go over some of this information in detail later in this and the next chapter. For now we will just use the Observer to look @@ -358,7 +358,7 @@ at the running processes. First we take a look at the `Applications` tab which shows the supervision tree of the running system: -image::images/observer_applications.png[] +image::../images/observer_applications.png[] Here we get a graphical view of how the processes are linked. This is a very nice way to get an overview of how a system is structured. @@ -368,7 +368,7 @@ floating in space connected to each other through links. To actually get some useful information about the processes we switch to the `Processes` tab: -image::images/observer_processes.png[] +image::../images/observer_processes.png[] In this view we get basically the same information as with `i/0` in the shell. We see the pid, the registered name, @@ -379,7 +379,7 @@ We can also look into a process by double clicking on its row, for example on the code server, to get the kind of information you can get with `process_info/2`: -image::images/observer_code_server.png[] +image::../images/observer_code_server.png[] We will not go through what all this information means right now, but if you keep on reading all will eventually