start.rst (1886B)
1 Getting started 2 --------------- 3 4 Prior to using any GNUnet-based application, one has to start a node: 5 6 :: 7 8 $ gnunet-arm -s 9 10 To stop GNUnet: 11 12 :: 13 14 $ gnunet-arm -e 15 16 You can usually find the logs under ``~/.cache/gnunet`` and all files 17 such as databases and private keys in ``~/.local/share/gnunet``. 18 19 The list of running services can be displayed using the ``-I`` option. 20 It should look similar to this example: 21 22 :: 23 24 $ gnunet-arm -I 25 Running services: 26 topology (gnunet-daemon-topology) 27 nat (gnunet-service-nat) 28 vpn (gnunet-service-vpn) 29 gns (gnunet-service-gns) 30 cadet (gnunet-service-cadet) 31 namecache (gnunet-service-namecache) 32 hostlist (gnunet-daemon-hostlist) 33 revocation (gnunet-service-revocation) 34 zonemaster (gnunet-service-zonemaster) 35 zonemaster-monitor (gnunet-service-zonemaster-monitor) 36 dht (gnunet-service-dht) 37 namestore (gnunet-service-namestore) 38 set (gnunet-service-set) 39 statistics (gnunet-service-statistics) 40 nse (gnunet-service-nse) 41 fs (gnunet-service-fs) 42 peerstore (gnunet-service-peerstore) 43 core (gnunet-service-core) 44 rest (gnunet-rest-server) 45 transport (gnunet-service-transport) 46 datastore (gnunet-service-datastore) 47 48 For the **multi-user** setup first the system services need to be 49 started as the system user, i.e. the user gnunet needs to execute 50 ``gnunet-arm -s``. This should be done by the system’s init system. Then 51 the user who wants to start GNUnet applications has to run 52 ``gnunet-arm -s``, too. It is recommended to automate this, e.g. using 53 the user’s crontab. 54 55 You can check directly connected peers with: 56 57 :: 58 59 $ gnunet-core --connection-status 60 61 This should return (at least) one established connection peer. 62 Otherwise, again, there is likely a problem with your network 63 configuration. 64 65 You can display your own current peer identity with: 66 67 :: 68 69 $ gnunet-core --show-identity