Stopping and restarting Yate
(→Yate as a service) |
|||
| Line 1: | Line 1: | ||
| + | There are different ways of stopping and restarting Yate depending on how Yate was installed and configured. | ||
=== Signals and keys for a running Yate=== | === Signals and keys for a running Yate=== | ||
Revision as of 17:29, 15 January 2013
There are different ways of stopping and restarting Yate depending on how Yate was installed and configured.
Contents |
Signals and keys for a running Yate
While running the following signals and keys are trapped and used:
- SIGTERM and SIGINT (Ctrl-C) will cleanly stop the engine - SIGHUP and SIGQUIT (Ctrl-\) will reinitialize the modules
Telnet commands
If you have rmanager module enabled, you can also connect to port 5038 and use command "stop" to stop the engine, and "reload" to reload the configurations.
Note that the modules are not reloaded, only their configuration files are read. Also note that some modules have options that are read only on the first initialization.
Yate started in supervised mode
If Yate is started in supervised mode (command line option -s) it can also be restarted from rmanager using "stop 128" - in fact any code between 128 and 255. The program will be stopped cleanly then the supervisor will restart it with the same command line options.
Yate started as a service
If Yate was set as a service use commands:
service yate stop service yate restart
As a general note, use restart instead of start to avoid accidentally running multiple instances.
