Dincho Todorov

@mitchelli could you please double check if the socket configuration includes `SO_REUSEADDR` ?

In general the clients/server are expected to have long running open connections which should work fine, but in case they need to reconnect (fast) for some reason, it's probably too...

> I'm not sure why the client can tell the node to listen on a certain port. Ah, now I remember! This is how it works currently as the SC...

This ticket is more or less for me too keep investigating why it could not run it with other users (given they have rx permissions). The node should not write...

Yes, that would be my expectation, we already have a configuration option to disable database persistence which works as expected so far. I can't think of any other module that...

> Note: when launching in the background (with the 'start' or 'daemon' flags), this is done via the `run_erl` shim, which disconnects stdin and attaches stdout and stderr to disk...

Use-case ?

> Every node response may contain the height and microblock number. You can get that already via the API no? In general this won't work with caching.

A release note is somehow important for this change IMO, although it is BC

I meant LICENSE file in the root dir of the repo, we're using automated tools to monitor our vendor licenses (versioneye.com). Do you want me to open PR with this?