11. Database Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 11.1. Database Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 11.3. New Startup and Shutdown States in Firebird 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -at(tach) shutdown new database attachments -b(uffers) set page buffers -co(mmit) commit transaction -ca(che) shutdown cache manager -fu(ll)

--help' for help on a specific command. 8 QUICK START Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. karaf@root()> SOME SHELL BASICS You can now run your first command. Simply console, enter ^D in the console: ^D Alternatively, you can also run the following command: system:shutdown Cleaning the Karaf state Normally Karaf remembers the features and bundles you installed and started commands and '[cmd] --help' for help on a specific command. Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. karaf@root()> On Windows: bin\karaf.bat __ __ ____ / //_/____

commands and '[cmd] --help' for help on a specific command. Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. karaf@root()> You can then grab more specific help for a given command using shell:threads shell:watch shell:wc shell:while shutdown sleep sort source ssh system:framework system:name system:property system:shutdown system:start-level system:version tac tail threads

time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event multi stop w1 -A proj -l info The stop command is asynchronous so it won’t wait for the worker to shutdown. You’ll probably want to use the stopwait command instead, this ensures all currently executing

time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event It’s easy to start multiple workers by accident, so make sure that the previous worker is properly shutdown before you start a new one. An old worker that aren’t configured with the expected result backend

time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event It’s easy to start multiple workers by accident, so make sure that the previous worker is properly shutdown before you start a new one. An old worker that aren’t configured with the expected result backend

time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event It’s easy to start multiple workers by accident, so make sure that the previous worker is properly shutdown before you start a new one. An old worker that aren’t configured with the expected result backend

time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event It’s easy to start multiple workers by accident, so make sure that the previous worker is properly shutdown before you start a new one. An old worker that aren’t configured with the expected result backend

time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event time of the longest ETA you’re planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event It’s easy to start multiple workers by accident, so make sure that the previous worker is properly shutdown before you start a new one. An old worker that aren’t configured with the expected result backend

Started 15 Celery Documentation, Release 3.1.25 Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event of the longest ETA you are planning to use. Note that Celery will redeliver messages at worker shutdown, so having a long visibility timeout will only delay the redelivery of ‘lost’ tasks in the event It’s easy to start multiple workers by accident, so make sure that the previous worker is properly shutdown before you start a new one. An old worker that is not configured with the expected result backend