aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2015-03-23 12:07:52 +0000
committerChristian Grothoff <christian@grothoff.org>2015-03-23 12:07:52 +0000
commit1bbe97fc3dcf3436e5e07e715c03901e1f18e4b6 (patch)
treeecdc16d3c012aa0b52f9826c41e2a9c37ee09031
parentc77d4e5c69ac54ffddf5bd60c18bcb0504389311 (diff)
downloadgnunet-1bbe97fc3dcf3436e5e07e715c03901e1f18e4b6.tar.gz
gnunet-1bbe97fc3dcf3436e5e07e715c03901e1f18e4b6.zip
-update doc
-rw-r--r--doc/gnunet-c-tutorial.tex24
1 files changed, 14 insertions, 10 deletions
diff --git a/doc/gnunet-c-tutorial.tex b/doc/gnunet-c-tutorial.tex
index 83a740c99..ee24b0ae4 100644
--- a/doc/gnunet-c-tutorial.tex
+++ b/doc/gnunet-c-tutorial.tex
@@ -270,25 +270,29 @@ SERVERS = # prevent bootstrapping
270\subsection{Start a peer} 270\subsection{Start a peer}
271Each GNUnet instance (called peer) has an identity (\textit{peer ID}) based on a 271Each GNUnet instance (called peer) has an identity (\textit{peer ID}) based on a
272cryptographic public private key pair. The peer ID is the printable hash of the 272cryptographic public private key pair. The peer ID is the printable hash of the
273public key. So before starting the peer, you may want to just generate the peer's private 273public key.
274key using the command 274
275GNUnet services are controlled by a master service the so called \textit{Automatic Restart Manager} (ARM).
276ARM starts, stops and even restarts services automatically or on demand when a client connects.
277You interact with the ARM service using the \lstinline|gnunet-arm| tool.
278GNUnet can then be started with \lstinline|gnunet-arm -s| and stopped with
279\lstinline|gnunet-arm -e|. An additional service not automatically started
280can be started using \lstinline|gnunet-arm -i <service name>| and stopped
281using \lstinline|gnunet-arm -k <servicename>|.
282
283Once you have started your peer, you can use many other GNUnet commands
284to interact with it. For example, you can run:
275\lstset{language=bash} 285\lstset{language=bash}
276\begin{lstlisting} 286\begin{lstlisting}
277$ gnunet-peerinfo -c ~/peer1.conf -s 287$ gnunet-peerinfo -s
278\end{lstlisting} 288\end{lstlisting}
289to obtain the public key of your peer.
279You should see an output containing the peer ID similar to: 290You should see an output containing the peer ID similar to:
280\lstset{language=bash} 291\lstset{language=bash}
281\begin{lstlisting} 292\begin{lstlisting}
282I am peer `0PA02UVRKQTS2C .. JL5Q78F6H0B1ACPV1CJI59MEQUMQCC5G'. 293I am peer `0PA02UVRKQTS2C .. JL5Q78F6H0B1ACPV1CJI59MEQUMQCC5G'.
283\end{lstlisting} 294\end{lstlisting}
284 295
285GNUnet services are controlled by a master service the so called \textit{Automatic Restart Manager} (ARM).
286ARM starts, stops and even restarts services automatically or on demand when a client connects.
287You interact with the ARM service using the \lstinline|gnunet-arm| tool.
288GNUnet can then be started with \lstinline|gnunet-arm -s| and stopped with
289\lstinline|gnunet-arm -e|. An additional service not automatically started
290can be started using \lstinline|gnunet-arm -i <service name>| and stopped
291using \lstinline|gnunet-arm -k <servicename>|.
292 296
293\subsection{Monitor a peer} 297\subsection{Monitor a peer}
294In this section, we will monitor the behaviour of our peer's DHT service with respect to a 298In this section, we will monitor the behaviour of our peer's DHT service with respect to a