summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorpsyc://loupsycedyglgamf.onion/~lynX <ircs://psyced.org/youbroketheinternet>1984-04-04 00:44:05 +0000
committerpsyc://loupsycedyglgamf.onion/~lynX <ircs://psyced.org/youbroketheinternet>1984-04-04 00:44:04 +0000
commite73402fc3a6f233b48330435f61ccd93722ac0e5 (patch)
treec63db5153cca3e3aeda01a18a2bad5785b02ecb3 /doc
parent99c6e18e63181d8759ecbb398d58019a55d3ce6f (diff)
rename FORCESTART into IMMEDIATE_START (#4547b)
Diffstat (limited to 'doc')
-rw-r--r--doc/documentation/chapters/developer.texi8
-rw-r--r--doc/documentation/chapters/user.texi2
-rw-r--r--doc/documentation/gnunet-c-tutorial.texi2
-rw-r--r--doc/man/gnunet-auto-share.12
-rw-r--r--doc/man/gnunet-namestore-fcfsd.12
-rw-r--r--doc/man/gnunet.conf.58
6 files changed, 12 insertions, 12 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi
index f4c954509..22b175a3f 100644
--- a/doc/documentation/chapters/developer.texi
+++ b/doc/documentation/chapters/developer.texi
@@ -2297,15 +2297,15 @@ is to set
@example
[core]
-FORCESTART = YES
+IMMEDIATE_START = YES
@end example
@noindent
in the configuration file.
Alternatively, having any service that directly or indirectly depends on
-@code{CORE} being started with @code{FORCESTART} will also do.
+@code{CORE} being started with @code{IMMEDIATE_START} will also do.
This issue largely arises if users try to over-optimize by not
-starting any services with @code{FORCESTART}.
+starting any services with @code{IMMEDIATE_START}.
@c ***********************************************************************
@node ATS must want the connections
@@ -3705,7 +3705,7 @@ running a service with "valgrind" or "gdb"
@item START_ON_DEMAND ARM will listen to UNIX domain socket and/or TCP port of
the service and start the service on-demand.
-@item FORCESTART ARM will always start this service when the peer
+@item IMMEDIATE_START ARM will always start this service when the peer
is started.
@item ACCEPT_FROM IPv4 addresses the service accepts connections from.
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi
index 3b829559b..3d4f55e41 100644
--- a/doc/documentation/chapters/user.texi
+++ b/doc/documentation/chapters/user.texi
@@ -3703,7 +3703,7 @@ gnunet-arm -c ~/.config/gnunet.conf -k fs
@noindent
Assuming that you want certain services (like file-sharing) to be always
automatically started whenever you start GNUnet, you can activate them by
-setting "FORCESTART=YES" in the respective section of the configuration
+setting "IMMEDIATE_START=YES" in the respective section of the configuration
file (for example, "[fs]"). Then GNUnet with file-sharing support would
be started whenever you@ enter:
diff --git a/doc/documentation/gnunet-c-tutorial.texi b/doc/documentation/gnunet-c-tutorial.texi
index 0e2adaee7..fb6e717ae 100644
--- a/doc/documentation/gnunet-c-tutorial.texi
+++ b/doc/documentation/gnunet-c-tutorial.texi
@@ -647,7 +647,7 @@ If you want to use the @code{peerinfo} tool to connect your
peers, you should:
@itemize
-@item Set @code{FORCESTART = NO} in section @code{hostlist}
+@item Set @code{IMMEDIATE_START = NO} in section @code{hostlist}
(to not connect to the global GNUnet)
@item Start both peers running @command{gnunet-arm -c peer1.conf -s}
and @command{gnunet-arm -c peer2.conf -s}
diff --git a/doc/man/gnunet-auto-share.1 b/doc/man/gnunet-auto-share.1
index f655f6ccd..fc2668d44 100644
--- a/doc/man/gnunet-auto-share.1
+++ b/doc/man/gnunet-auto-share.1
@@ -111,7 +111,7 @@ Share a directory "$HOME/gnunet\-share/":
[gnunet-auto-share]
OPTIONS = $HOME/gnunet\-share
- FORCESTART = YES # start this service when the peer starts
+ IMMEDIATE_START = YES # start this service when the peer starts
.SH FILES
.TP
diff --git a/doc/man/gnunet-namestore-fcfsd.1 b/doc/man/gnunet-namestore-fcfsd.1
index 7fc4093c2..88ab72071 100644
--- a/doc/man/gnunet-namestore-fcfsd.1
+++ b/doc/man/gnunet-namestore-fcfsd.1
@@ -20,7 +20,7 @@ configuration file in section "[fcfsd]" under the name "HTTPPORT".
It is possible to manage gnunet\-gns\-fcfsd using
gnunet\-(service\-arm) by starting the daemon using "gnunet\-arm \-i
-fcfsd" or by setting "FORCESTART=YES" in the "fcfds" section of your
+fcfsd" or by setting "IMMEDIATE_START=YES" in the "fcfds" section of your
configuration and the "-z ZONE" in as the "OPTION".
An FCFS\-zone is run at http://gnunet.org/fcfs/. GNS users are
diff --git a/doc/man/gnunet.conf.5 b/doc/man/gnunet.conf.5
index b0f1c152c..3dd8c7b62 100644
--- a/doc/man/gnunet.conf.5
+++ b/doc/man/gnunet.conf.5
@@ -55,7 +55,7 @@ The following options are generic and shared by all services:
This is usually "localhost".
.IP BINARY
The filename that implements the service. For example "gnunet-service-ats".
-.IP FORCESTART
+.IP IMMEDIATE_START
Start the service always when the peer starts. Set to YES for services
that should always be launched, even if no other service explicitly needs
them.
@@ -66,13 +66,13 @@ The following options are generic and shared by all services:
Set to YES to never have ARM bind to the respective socket. This option is
mostly for debugging in situations where ARM cannot pass the pre-bound
socket to the child due to interference from PREFIX-commands.
- This option is only effective in combination with FORCESTART being YES.
+ This option is only effective in combination with IMMEDIATE_START being YES.
NO by default.
.IP PREFIX
PREFIX the given command (with its arguments) to the actual BINARY to be
executed. Useful to run certain services under special supervisors (like
- strace or valgrind). Typically used in combination with FORCESTART and
- NOARMBIND. Empty by default.
+ strace or valgrind). Typically used in combination with IMMEDIATE_START
+ and NOARMBIND. Empty by default.
.IP ACCEPT_FROM
A semi-column separated list of IPv4 addresses that are allowed to use
the service; usually 127.0.0.1.