diff options
| author | Julius Bünger <buenger@mytum.de> | 2018-09-26 20:32:59 +0200 |
|---|---|---|
| committer | Julius Bünger <buenger@mytum.de> | 2018-09-26 20:40:58 +0200 |
| commit | 1d724e33b5f1eef331be967665e603cc12e6a375 (patch) | |
| tree | d71203831d5485e3e555d6454cb9e5e47d74eb76 /src | |
| parent | d691980cefc24464dcd85d8f1fae84d906bd7eb1 (diff) | |
| download | gnunet-1d724e33b5f1eef331be967665e603cc12e6a375.tar.gz gnunet-1d724e33b5f1eef331be967665e603cc12e6a375.zip | |
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).
Diffstat (limited to 'src')
| -rw-r--r-- | src/rps/rps.conf.in | 1 |
1 files changed, 1 insertions, 0 deletions
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 @@ | |||
| 1 | [rps] | 1 | [rps] |
| 2 | START_ON_DEMAND = @START_ON_DEMAND@ | 2 | START_ON_DEMAND = @START_ON_DEMAND@ |
| 3 | FORCESTART = YES | ||
| 3 | BINARY = gnunet-service-rps | 4 | BINARY = gnunet-service-rps |
| 4 | UNIXPATH = $GNUNET_RUNTIME_DIR/gnunet-service-rps.sock | 5 | UNIXPATH = $GNUNET_RUNTIME_DIR/gnunet-service-rps.sock |
| 5 | HOME = $SERVICEHOME | 6 | HOME = $SERVICEHOME |