Stopping and restarting Yate
(→Yate as a service) |
(→Yate as a service) |
||
| Line 18: | Line 18: | ||
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. | 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 as a service=== | + | === Yate started as a service=== |
If Yate was set as a service use commands: | If Yate was set as a service use commands: | ||
Revision as of 17:24, 15 January 2013
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.
