aboutsummaryrefslogtreecommitdiff
path: root/doc/man/gnunet-publish.1
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/gnunet-publish.1')
-rw-r--r--doc/man/gnunet-publish.14
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man/gnunet-publish.1 b/doc/man/gnunet-publish.1
index ff37610ff..eee24c8d7 100644
--- a/doc/man/gnunet-publish.1
+++ b/doc/man/gnunet-publish.1
@@ -25,7 +25,7 @@ You can use automatic meta\-data extraction (based on libextractor) or the comma
25GNUnet supports two styles of publishing files on the network. Publishing a file means that a copy of the file is made in the local (!) database of the node. Indexing a file means that an index is added to the local (!) database with symbolic links to the file itself. The links will use the SHA-512 hash of the entire file as the filename. Indexing is generally significantly more efficient and the default choice. However, indexing only works if the indexed file can be read (using the same absolute path) by gnunet-service-fs. If this is not the case, indexing will fail (and gnunet\-publish will automatically revert to publishing instead). Regardless of which method is used to publish the file, the file will be slowly (depending on how often it is requested and on how much bandwidth is available) dispersed into the network. If you publish or index a file and then leave the network, it will almost always NOT be available anymore. 25GNUnet supports two styles of publishing files on the network. Publishing a file means that a copy of the file is made in the local (!) database of the node. Indexing a file means that an index is added to the local (!) database with symbolic links to the file itself. The links will use the SHA-512 hash of the entire file as the filename. Indexing is generally significantly more efficient and the default choice. However, indexing only works if the indexed file can be read (using the same absolute path) by gnunet-service-fs. If this is not the case, indexing will fail (and gnunet\-publish will automatically revert to publishing instead). Regardless of which method is used to publish the file, the file will be slowly (depending on how often it is requested and on how much bandwidth is available) dispersed into the network. If you publish or index a file and then leave the network, it will almost always NOT be available anymore.
26 26
27\fB\-c \fIFILENAME\fR, \fB\-\-config=FILENAME\fR 27\fB\-c \fIFILENAME\fR, \fB\-\-config=FILENAME\fR
28Use alternate config file (if this option is not specified, the default is ~/.gnunet/gnunet.conf). 28Use alternate config file (if this option is not specified, the default is ~/.config/gnunet.conf).
29 29
30.TP 30.TP
31\fB\-D\fR, \fB\-\-disable\-extractor\fR 31\fB\-D\fR, \fB\-\-disable\-extractor\fR
@@ -164,7 +164,7 @@ Update the previous entry, do not allow any future updates:
164 164
165.SH FILES 165.SH FILES
166.TP 166.TP
167~/.gnunet/gnunet.conf 167~/.config/gnunet.conf
168GNUnet configuration file 168GNUnet configuration file
169.SH "REPORTING BUGS" 169.SH "REPORTING BUGS"
170Report bugs to <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet\-developers@gnu.org> 170Report bugs to <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet\-developers@gnu.org>