aboutsummaryrefslogtreecommitdiff
path: root/doc/man/gnunet-namestore-fcfsd.1
blob: a6c9d2b3243b0db88b22b974ca9be2e0c754d18b (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
.TH GNUNET-NAMESTORE-FCFSD 1 "September 5, 2013" "GNUnet"
.SH NAME
gnunet\-namestore-fcfsd \- HTTP server for GNU Name System First-Come-First-Served name registration
.SH SYNOPSIS
.B gnunet\-namestore-fcfsd
.RI [ options ]
.SH DESCRIPTION
Most users will not want to run an FCFS\-zone and thus will not need
this program.
.PP
\fBgnunet\-gns-fcfsd\fP runs a web server where users can register
names to be mapped to their GNS zone.  Names are made available on a
First Come First Served basis (hence fcfs).  Registered names do not
expire.  The HTTP server is run on the port that is specified in the
configuration file in section "[fcfsd]" under the name "HTTPPORT".
.PP
It is possible to manage gnunet\-gns\-fcfsd using
gnunet\-(service\-arm) by starting the daemon using "gnunet\-arm \-i
fcfsd" or by setting "IMMEDIATE_START=YES" in the "fcfds" section of your
configuration and the "-z ZONE" in as the "OPTION".
.PP
An FCFS\-zone is run at http://gnunet.org/fcfs/.  GNS users are
encouraged to register their zone with the gnunet.org FCFS authority.
.PP
If you want to run your own FCFS registrar, you need to first create a
pseudonym (using "gnunet\-identity \-C NAME"), and use it with the
"-z" option.  After that, you can start the FCFSD service (possibly using
gnunet\-arm).
.SH OPTIONS
.B
.IP "\-c FILENAME,  \-\-config=FILENAME"
Use the configuration file FILENAME.
.B
.IP "\-h, \-\-help"
Print short help on options.
.B
.IP "\-L LOGLEVEL, \-\-loglevel=LOGLEVEL"
Use LOGLEVEL for logging.  Valid values are DEBUG, INFO, WARNING and
ERROR.
.B
.IP "\-v, \-\-version"
Print GNUnet version number.
.B
.IP "\-z EGO, \-\-zone=EGO"
Specifies for which EGO should FCFSD manage the zone.
.SH BUGS
Report bugs by using Mantis <https://bugs.gnunet.org/> or by sending
electronic mail to <bug\-gnunet@gnu.org>
.SH SEE ALSO
gnunet\-identity(1), gnunet\-gns(1), gnunet\-gns\-proxy(1)
.PP
The full documentation for
.B gnunet
is maintained as a Texinfo manual.
If the
.B info
and
.B gnunet
programs are properly installed at your site, the command
.IP
.B info gnunet
.PP
should give you access to the complete handbook,
.IP
.B info gnunet-c-tutorial
.PP
will give you access to a tutorial for developers.
.PP
Depending on your installation, this information is also
available in
\fBgnunet\fP(7) and \fBgnunet-c-tutorial\fP(7).