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).

diff --git a/src/rps/rps.conf.in b/src/rps/rps.conf.in
index 7f0a419bd0130f52395418e1891c75fa71cd4565..1b63849e6e911ba05488987690d79ddceb48ec59 100644 (file)
--- 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