gnunet-handbook

commit ae9976551b142d02053ca07239975fa6155cdf77
parent c3b21295355c7d9e6d8f1e5c927f05df502120ab
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Thu, 13 Jun 2024 21:05:14 +0200

update gnunet-core API in start

Diffstat:
M
users/start.rst
 | 
21
++++++++-------------

1 file changed, 8 insertions(+), 13 deletions(-)
diff --git a/users/start.rst b/users/start.rst
@@ -31,8 +31,6 @@ It should look similar to this example:
    namecache (gnunet-service-namecache)
    hostlist (gnunet-daemon-hostlist)
    revocation (gnunet-service-revocation)
-   ats (gnunet-service-ats)
-   peerinfo (gnunet-service-peerinfo)
    zonemaster (gnunet-service-zonemaster)
    zonemaster-monitor (gnunet-service-zonemaster-monitor)
    dht (gnunet-service-dht)
@@ -54,21 +52,18 @@ the user who wants to start GNUnet applications has to run
 ``gnunet-arm -s``, too. It is recommended to automate this, e.g. using
 the user’s crontab.
 
-First, you should launch the peer information tool. You can do this from
-the command-line by typing:
+You can check directly connected peers with:
 
 ::
 
-   $ gnunet-peerinfo
-
-Once you have done this, you will see a list of known peers. If hardly
-any peers are listed, there is likely a problem with your network
-configuration. You can also check directly connected peers with:
-
-::
-
-   $ gnunet-core
+   $ gnunet-core --connection-status
 
 This should return (at least) one established connection peer.
 Otherwise, again, there is likely a problem with your network
 configuration.
+
+You can display your own current peer identity with:
+
+::
+
+  $ gnunet-core --show-identity