Prevent CLI from throwing errors altogether.

[davidjbeveridge]

The issue I was having was that if I ran node server.js status, I would get
this error:

./node_modules/clu/lib/commandLine.js:209
    else throw err;
               ^
Error: connect ENOENT
    at errnoException (net.js:901:11)
    at Object.afterConnect [as oncomplete] (net.js:892:19)

I haven't been able to figure out how to directly execute the status command,
and thus, haven't been able to add a proper test. Any help here would be
greatly appreciated.

[fiws]

Hello,

thank you for contributing and pointing out this bug! 👍
Error: connect ENOENT probably gets thrown because the master is not running. This happens if you use unix sockets to connect (which clu will use by default). Clu still should not throw in this case. I fixed this in the last commits.

If you still experience this problem, feel free to contact me again. :)