Better handling of already running ipfs daemon

[jbenet]

[jbenet]

i think it was when i started this node while a background daemon was running?

[caioalonso]

+1

These are the steps that I did:

1. $ ipfs daemon
2. $ npm start
3. Turn IPFS Node on
4. Ctrl-C the daemon

[jbenet]

this thing runs its own daemon. you dont need to run it yourself. it's port clashing

also, we need a waaaay better error for that. ugh

[caioalonso]

@jbenet yes, a simple port conflict shouldn't crash it.

[hacdias]

Already a bit better than what it was in 2015. Although, there is still a lot of room to improvement. Will continue this on #527.