From e73402fc3a6f233b48330435f61ccd93722ac0e5 Mon Sep 17 00:00:00 2001 From: "psyc://loupsycedyglgamf.onion/~lynX" Date: Wed, 4 Apr 1984 00:44:05 +0000 Subject: rename FORCESTART into IMMEDIATE_START (#4547b) --- doc/documentation/chapters/developer.texi | 8 ++++---- doc/documentation/chapters/user.texi | 2 +- doc/documentation/gnunet-c-tutorial.texi | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) (limited to 'doc/documentation') 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} -- cgit v1.2.3