diff options
Diffstat (limited to 'doc/documentation')
-rw-r--r-- | doc/documentation/chapters/developer.texi | 27 |
1 files changed, 18 insertions, 9 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi index befc135b0..21c158998 100644 --- a/doc/documentation/chapters/developer.texi +++ b/doc/documentation/chapters/developer.texi | |||
@@ -1896,16 +1896,25 @@ subsystem. | |||
1896 | @node CORE must be started | 1896 | @node CORE must be started |
1897 | @subsubsection CORE must be started | 1897 | @subsubsection CORE must be started |
1898 | 1898 | ||
1899 | A simple issue is #3993: Your configuration MUST somehow ensure that for | 1899 | A uncomplicated issue is bug #3993@footnote{@uref{https://gnunet.org/bugs/view.php?id=3993, https://gnunet.org/bugs/view.php?id=3993}}: |
1900 | each peer the CORE service is started when the peer is setup, otherwise | 1900 | Your configuration MUST somehow ensure that for each peer the |
1901 | TESTBED may fail to connect peers when the topology is initialized, as | 1901 | @code{CORE} service is started when the peer is setup, otherwise |
1902 | TESTBED will start some CORE services but not necessarily all (but it | 1902 | @code{TESTBED} may fail to connect peers when the topology is initialized, |
1903 | relies on all of them running). The easiest way is to set | 1903 | as @code{TESTBED} will start some @code{CORE} services but not |
1904 | 'FORCESTART = YES' in the '[core]' section of the configuration file. | 1904 | necessarily all (but it relies on all of them running). The easiest way |
1905 | is to set | ||
1906 | |||
1907 | @example | ||
1908 | [core] | ||
1909 | FORCESTART = YES | ||
1910 | @end example | ||
1911 | |||
1912 | @noindent | ||
1913 | in the configuration file. | ||
1905 | Alternatively, having any service that directly or indirectly depends on | 1914 | Alternatively, having any service that directly or indirectly depends on |
1906 | CORE being started with FORCESTART will also do. This issue largely arises | 1915 | @code{CORE} being started with @code{FORCESTART} will also do. |
1907 | if users try to over-optimize by not starting any services with | 1916 | This issue largely arises if users try to over-optimize by not |
1908 | FORCESTART. | 1917 | starting any services with @code{FORCESTART}. |
1909 | 1918 | ||
1910 | @c *********************************************************************** | 1919 | @c *********************************************************************** |
1911 | @node ATS must want the connections | 1920 | @node ATS must want the connections |