nodejitsu/forever — pull request #633 by Tjatse (2014-11-10 09:11:58+00:00)
Title: [update] restart series

I.E.:
- The sockets are forced ranking by created time now.
- Print processing information:

```
$ forever restartall
info: Stopping test/fixtures/cluster-fork-mode.js
info: Stopping test/fixtures/log-on-interval.js
info: Stopping test/fixtures/server.js
info: Forever stopped processes:
data: uid command script forever pid id logfile uptime
data: [0] b2lT /usr/local/bin/node test/fixtures/cluster-fork-mode.js 71227 71228 /Users/tjatse/.forever/b2lT.log STOPPED
data: [1] 4L6o /usr/local/bin/node test/fixtures/log-on-interval.js 71268 71269 /Users/tjatse/.forever/4L6o.log 0:0:0:10.355
data: [2] rypa /usr/local/bin/node test/fixtures/server.js 71272 71273 /Users/tjatse/.forever/rypa.log STOPPED
```

- When `$ forever restartall` or `$ forever stopall` is being executed, we restart each worker one by one, but not all at once, it makes a bad experience especially workers have successively dependencies - *workers[1] dependents on workers[2], workers[3] deps on workers[2]...*
- Delay betweens each restart/stop operation can be customized now, `config interval`, this helps a lot when workers need warm-up.