[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet] branch master updated: Start rps in any case
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet] branch master updated: Start rps in any case |
Date: |
Wed, 26 Sep 2018 20:41:16 +0200 |
This is an automated email from the git hooks/post-receive script.
julius-buenger pushed a commit to branch master
in repository gnunet.
The following commit(s) were added to refs/heads/master by this push:
new 1d724e33b Start rps in any case
1d724e33b is described below
commit 1d724e33b5f1eef331be967665e603cc12e6a375
Author: Julius Bünger <address@hidden>
AuthorDate: Wed Sep 26 20:32:59 2018 +0200
Start rps in any case
Starting rps makes sense as
- it is still experimental. It will only run for the persons having
configured with --enable-experimental and be quite useful for
developement.
- starting rps on-demand does not make sense in production as the
service can already participate in the gossip meaning that it is
already represented at other peers and already gathers information
about other peers.
The earlier it starts participating in the gossip, the more secure
the gossiping will be for all participants.
- it only consumes few resources (at least it should).
---
src/rps/rps.conf.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/rps/rps.conf.in b/src/rps/rps.conf.in
index 7f0a419bd..1b63849e6 100644
--- a/src/rps/rps.conf.in
+++ b/src/rps/rps.conf.in
@@ -1,5 +1,6 @@
[rps]
START_ON_DEMAND = @START_ON_DEMAND@
+FORCESTART = YES
BINARY = gnunet-service-rps
UNIXPATH = $GNUNET_RUNTIME_DIR/gnunet-service-rps.sock
HOME = $SERVICEHOME
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [gnunet] branch master updated: Start rps in any case,
gnunet <=