Although Control-D can be used, for some users it would be good for them to know that they can also just type `.exit`
Since quit is a common command to exit certain types of command shells, I felt it would be better to use a different name for stopping the cluster, since it would be easy to get confused and accidentally shut down the cluster when simply wanting to exit the REPL shell. I switched the REPL command to stop() for a graceful shutdown and a kill() for stopping hard.
Allow `repl` config option passed into clusterMaster constructor * `repl` - where to have REPL listen, defaults to `env.CLUSTER_MASTER_REPL` || 'cluster-master-socket' * if `repl` is null or false - REPL is disabled and will not be started * if `repl` is string path - REPL will listen on unix domain socket to this path * if `repl` is an integer port - REPL will listen on TCP 0.0.0.0:port * if `repl` is an object with `address` and `port`, then REPL will listen on TCP address:PORT
Describe how you use the REPL, how to change the path of the socket, and lists commands you can use in the REPL
If the connection to iriscouch hiccups, it can tank the npm-www website. A worker will die, then restart badly, and the master would just give up too quickly and end up in a state where it had no workers, and was not serving any requests. Instead, be a little more pushy about trying to restart, and then kill the *master* if it fails repeatedly, so that the crash is reported to the system, and SMF/upstart/whatever can take over.
Make it easier to get relevant info about the workers
Now the module can at least bootstrap itself without crashing on Windows. Related: joyent/node#2904
Also, some basic cleanup and using the proper APIs for things.