diff options
Diffstat (limited to 'doc/chapters')
-rw-r--r-- | doc/chapters/installation.texi | 27 |
1 files changed, 13 insertions, 14 deletions
diff --git a/doc/chapters/installation.texi b/doc/chapters/installation.texi index 4b1db324f..5a84de52d 100644 --- a/doc/chapters/installation.texi +++ b/doc/chapters/installation.texi | |||
@@ -3897,13 +3897,13 @@ connecting to NATed peers using ICMP method" box. | |||
3897 | @node Peer configuration for distributions | 3897 | @node Peer configuration for distributions |
3898 | @subsection Peer configuration for distributions | 3898 | @subsection Peer configuration for distributions |
3899 | 3899 | ||
3900 | The "GNUNET_DATA_HOME" in "[path]" in /etc/gnunet.conf should be manually set | 3900 | The "GNUNET_DATA_HOME" in "[path]" in @file{/etc/gnunet.conf} should be manually set |
3901 | to "/var/lib/gnunet/data/" as the default "~/.local/share/gnunet/" is probably | 3901 | to "/var/lib/gnunet/data/" as the default "~/.local/share/gnunet/" is probably |
3902 | not that appropriate in this case. Similarly, distributions may consider | 3902 | not that appropriate in this case. Similarly, distributions may consider |
3903 | pointing "GNUNET_RUNTIME_DIR" to "/var/run/gnunet/" and "GNUNET_HOME" to | 3903 | pointing "GNUNET_RUNTIME_DIR" to "/var/run/gnunet/" and "GNUNET_HOME" to |
3904 | "/var/lib/gnunet/". Also, should a distribution decide to override system | 3904 | "/var/lib/gnunet/". Also, should a distribution decide to override system |
3905 | defaults, all of these changes should be done in a custom "/etc/gnunet.conf" | 3905 | defaults, all of these changes should be done in a custom @file{/etc/gnunet.conf} |
3906 | and not in the files in the "config.d/" directory. | 3906 | and not in the files in the @file{config.d/} directory. |
3907 | 3907 | ||
3908 | Given the proposed access permissions, the "gnunet-setup" tool must be run as | 3908 | Given the proposed access permissions, the "gnunet-setup" tool must be run as |
3909 | use "gnunet" (and with option "-c /etc/gnunet.conf" so that it modifies the | 3909 | use "gnunet" (and with option "-c /etc/gnunet.conf" so that it modifies the |
@@ -3922,7 +3922,7 @@ This section describes how to start a GNUnet peer. It assumes that you have | |||
3922 | already compiled and installed GNUnet and its' dependencies. Before you start a | 3922 | already compiled and installed GNUnet and its' dependencies. Before you start a |
3923 | GNUnet peer, you may want to create a configuration file using gnunet-setup | 3923 | GNUnet peer, you may want to create a configuration file using gnunet-setup |
3924 | (but you do not have to). Sane defaults should exist in your | 3924 | (but you do not have to). Sane defaults should exist in your |
3925 | @code{GNUNET_PREFIX/share/gnunet/config.d/} directory, so in practice you could | 3925 | @file{$GNUNET_PREFIX/share/gnunet/config.d/} directory, so in practice you could |
3926 | simply start without any configuration. If you want to configure your peer | 3926 | simply start without any configuration. If you want to configure your peer |
3927 | later, you need to stop it before invoking the @code{gnunet-setup} tool to | 3927 | later, you need to stop it before invoking the @code{gnunet-setup} tool to |
3928 | customize further and to test your configuration (@code{gnunet-setup} has | 3928 | customize further and to test your configuration (@code{gnunet-setup} has |
@@ -3954,12 +3954,12 @@ recommended. | |||
3954 | 3954 | ||
3955 | For the single-user setup, you do not need to do anything special and can just | 3955 | For the single-user setup, you do not need to do anything special and can just |
3956 | start the GNUnet background processes using @code{gnunet-arm}. By default, | 3956 | start the GNUnet background processes using @code{gnunet-arm}. By default, |
3957 | GNUnet looks in @code{~/.config/gnunet.conf} for a configuration (or | 3957 | GNUnet looks in @file{~/.config/gnunet.conf} for a configuration (or |
3958 | $XDG_CONFIG_HOME/gnunet.conf if@ $XDG_CONFIG_HOME is defined). If your | 3958 | @code{$XDG_CONFIG_HOME/gnunet.conf} if@ @code{$XDG_CONFIG_HOME} is defined). If your |
3959 | configuration lives elsewhere, you need to pass the @code{-c FILENAME} option | 3959 | configuration lives elsewhere, you need to pass the @code{-c FILENAME} option |
3960 | to all GNUnet commands. | 3960 | to all GNUnet commands. |
3961 | 3961 | ||
3962 | Assuming the configuration file is called @code{~/.config/gnunet.conf}, you | 3962 | Assuming the configuration file is called @file{~/.config/gnunet.conf}, you |
3963 | start your peer using the @code{gnunet-arm} command (say as user | 3963 | start your peer using the @code{gnunet-arm} command (say as user |
3964 | @code{gnunet}) using: | 3964 | @code{gnunet}) using: |
3965 | @example | 3965 | @example |
@@ -4017,7 +4017,7 @@ to automatically start your peer whenever your system boots. | |||
4017 | 4017 | ||
4018 | This requires you to create a user @code{gnunet} and an additional group | 4018 | This requires you to create a user @code{gnunet} and an additional group |
4019 | @code{gnunetdns}, prior to running @code{make install} during installation. | 4019 | @code{gnunetdns}, prior to running @code{make install} during installation. |
4020 | Then, you create a configuration file @code{/etc/gnunet.conf} which should | 4020 | Then, you create a configuration file @file{/etc/gnunet.conf} which should |
4021 | contain the lines:@ | 4021 | contain the lines:@ |
4022 | @code{@ | 4022 | @code{@ |
4023 | [arm]@ | 4023 | [arm]@ |
@@ -4029,7 +4029,7 @@ contain the lines:@ | |||
4029 | may also want to run @code{gnunet-setup} to configure your peer (databases, | 4029 | may also want to run @code{gnunet-setup} to configure your peer (databases, |
4030 | etc.). Make sure to pass @code{-c /etc/gnunet.conf} to all commands. If you | 4030 | etc.). Make sure to pass @code{-c /etc/gnunet.conf} to all commands. If you |
4031 | run @code{gnunet-setup} as user @code{gnunet}, you might need to change | 4031 | run @code{gnunet-setup} as user @code{gnunet}, you might need to change |
4032 | permissions on @code{/etc/gnunet.conf} so that the @code{gnunet} user can | 4032 | permissions on @file{/etc/gnunet.conf} so that the @code{gnunet} user can |
4033 | write to the file (during setup). | 4033 | write to the file (during setup). |
4034 | 4034 | ||
4035 | Afterwards, you need to perform another setup step for each normal user account | 4035 | Afterwards, you need to perform another setup step for each normal user account |
@@ -4038,7 +4038,7 @@ from which you want to access GNUnet. First, grant the normal user | |||
4038 | @code{@ | 4038 | @code{@ |
4039 | # adduser $USER gnunet@ | 4039 | # adduser $USER gnunet@ |
4040 | }@ | 4040 | }@ |
4041 | Then, create a configuration file in @code{~/.config/gnunet.conf} for the $USER | 4041 | Then, create a configuration file in @file{~/.config/gnunet.conf} for the $USER |
4042 | with the lines:@ | 4042 | with the lines:@ |
4043 | @code{@ | 4043 | @code{@ |
4044 | [arm]@ | 4044 | [arm]@ |
@@ -4148,9 +4148,9 @@ service. | |||
4148 | GNUnet's main services should be run as a separate user "gnunet" in a special | 4148 | GNUnet's main services should be run as a separate user "gnunet" in a special |
4149 | group "gnunet". The user "gnunet" should start the peer using "gnunet-arm -s" | 4149 | group "gnunet". The user "gnunet" should start the peer using "gnunet-arm -s" |
4150 | during system startup. The home directory for this user should be | 4150 | during system startup. The home directory for this user should be |
4151 | "/var/lib/gnunet" and the configuration file should be "/etc/gnunet.conf". Only | 4151 | @file{/var/lib/gnunet} and the configuration file should be @file{/etc/gnunet.conf}. |
4152 | the "gnunet" user should have the right to access "/var/lib/gnunet" (mode: | 4152 | Only the @code{gnunet} user should have the right to access @file{/var/lib/gnunet} |
4153 | 700). | 4153 | (@emph{mode: 700}). |
4154 | 4154 | ||
4155 | @node Recommendation - Control access to services using group "gnunet" | 4155 | @node Recommendation - Control access to services using group "gnunet" |
4156 | @subsubsection Recommendation - Control access to services using group "gnunet" | 4156 | @subsubsection Recommendation - Control access to services using group "gnunet" |
@@ -4201,4 +4201,3 @@ that group already exists (!). An alternative name for the "gnunetdns" group | |||
4201 | can be specified using the "--with-gnunetdns=GRPNAME" configure | 4201 | can be specified using the "--with-gnunetdns=GRPNAME" configure |
4202 | option. | 4202 | option. |
4203 | 4203 | ||
4204 | |||