Skip to content

Commit

Permalink
Fix relative paths for images in processes.asciidoc
Browse files Browse the repository at this point in the history
  • Loading branch information
ramkumarr authored and happi committed Jan 19, 2019
1 parent f12ee61 commit fcecb23
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions chapters/processes.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -350,15 +350,15 @@ 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
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.
Expand All @@ -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,
Expand All @@ -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
Expand Down

0 comments on commit fcecb23

Please sign in to comment.