| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | process: allow changing `exitCode` in `on('exit')` | Fedor Indutny | 2014-02-09 | 1 | -0/+11 |
| | | | | | fix #7081 | ||||
| * | process: use exit 1 for uncaughtException | isaacs | 2013-09-06 | 1 | -3/+3 |
| | | | | | | | | | | | | | Since it is Unix tradition to use exit code 1 for general-purpose script bail-out, and the way of doing that in Node is to throw an exception and not catch it, it makes the most sense to exit with 1 when an exception goes uncaught. Move the `Invalid Argument` exit to 9, so that it's something specific, and clear that it's a node internal error. Also, document the exit codes that we use. | ||||
| * | process: Use exit code 8 consistently | isaacs | 2013-09-06 | 1 | -1/+16 |
| | | | | | This should always be used in the case of an uncaughtException | ||||
| * | process: Add exitCode property | isaacs | 2013-09-06 | 1 | -0/+77 |
| This allows one to set a specific status code, while still letting the process exit gracefully once all async operations are completed. | |||||
 |
index : delta/node.git | |
| github.com: joyent/node.git |
| summaryrefslogtreecommitdiff |