-
Notifications
You must be signed in to change notification settings - Fork 512
Project control
The following scripts control a project:
Stop the project:
- Stop daemons
- Create the
stop_schedandstop_daemontrigger files (see below).
Start the project:
- Start daemons
- Remove the
stop_schedandstop_daemontrigger files.
- Show whether the project is stopped.
- Show the status of daemons.
- Show the status of periodic tasks (e.g., when they were last executed).
If the project is started, perform all periodic tasks that are past due, and start any daemons that aren't running. Otherwise do nothing.
Like --cron but doesn't start daemons.
The following files (in the project root directory) can be used to turn off various parts of a project.
Have the scheduler return 'project down' replies.
Tell all daemon process to exit.
Have the web site return 'project down' pages for all functions that require database access.
Have the file upload handler return transient error messages to clients (they'll back off and retry later).
Have the feeder reread the database to notice new applications, app versions, or changes to how work is assigned.
The presence of a file indicates the state. For example, to turn off data-driven web pages, type
touch stop_web
and to turn them back on, type
rm stop_web
If the first three files are all present, no database access will occur. You should do this during most maintenance functions (such as upgrading software).