mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
We try to kill any mongod processes before starting new ones, but this change kills it when the development server shuts down, too. Killing mongo on shutdown is particularly important for tests that run meteor multiple times in a row, and for whatever reason fail to find and kill running mongod processes on startup, e.g. because the --port has changed (#7563). This comment by @glasser seems to suggest this is a reasonable idea: https://github.com/meteor/meteor/issues/2182#issuecomment-45685614 Fixes #2182 and possibly other related bugs.
Runners
The Meteor tool process would run multiple big "parts" that should be managed: started, stopped, restarted, monitored for crashes, etc.
The interface that Meteor tool uses is called a "runner".
Some of the runners run sub-processes. The main runner is called run-all, it
has sub-runners such as run-app, run-mongo and run-proxy. Other runners
are used for different CLI commands.
Run Log
The output of the runners (compilation errors, state change, etc), should be reported through the Run Log. Run Log is also something that users see in their browsers, when their app breaks.