Thanks for the reply. I should have mentioned that when attempting to load / run the compiled slingd it uses 0% cpu and very very minimal memory with 0 connections after 20 hours with the same node list I'm using for my windows wallet. This is the same whether I start it in a screen session or run it as a background task
Did you :
cd ~/.sling
tail -f debug.log
to see what's happening?
A couple of ideas which may or may not help:
Run strip on the binary after compiling it, to dramatically decrease its size:
strip slingd
If you are behind a router (e.g. your home Linux machine, as opposed to a rented Linux VPS), compile using USE_UPNP=1:
make -f makefile.unix USE_UPNP=1
Run "slingd -daemon" to run it without having to background the process (&) or use nohup.
Good luck!
I had modified my conf file so many times at some point I had commented out daemon=1. Uncommenting it out fixed the "hang" -- oops
Then I noticed that it was getting hung up on 178.33.126.221:30137 with connection refused. Did a "slingd addnode 178.33.126.221:30137 remove", but at the same time added the nodes from