[bisq-network/bisq-docs] Updating the "How to Seednode" docs (#148)

Florian Reimair notifications at github.com
Sun Jul 28 22:01:28 UTC 2019

freimair commented on this pull request.

> +  git clone git at github.com:bisq-network/bisq.git
+  cd bisq
+  ./gradlew build -x test
+Create a systemd service file `bisq-seednode.service` (or copy the one shipped with bisq `$bisqdir/seednode/bisq-seednode.service`) in the systemd service path or your operating system (something like `/usr/lib/systemd/system/`) and adapt it to your needs.
+In the end, your file should look something like
+Description=Bisq Seed Node
+Environment="JAVA_OPTS=-Xms512M -Xmx2000M -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=6969 -Dcom.sun.management.jmxremote.rmi.port=6969 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
+ExecStart=/home/bisq/bisq/bisq-seednode --appName=bisq-seednode --nodePort=8000 --userDataDir=/home/bisq/ --maxConnections=50 --fullDaoNode=true --rpcUser=YOUR_USER_NAME --rpcPassword=YOUR_PW --rpcPort=8332 --rpcBlockNotificationPort=5120

Back when I ran 2 seed nodes, I had it set to 50 with only 800MB of Xmx and it worked without running out of memory. How about changing it to 30 and then adjust once we have a continuous heap space reading of the seed nodes?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190728/ac040914/attachment-0001.html>

More information about the bisq-github mailing list