iroffer v1.3 documentation - signal handling
| Notes about background mode and signal handling |
| Be sure iroffer isn't running before starting up another one. Since it is running in background mode, it wont be a child process of your shell so a "ps" probabily wont show it. You will need to do "ps -x" to get a list of all processes running under your username. |
| SIGUSR1 |
|
If iroffer gets stuck on some split/old server you can initialte a server switch by sending iroffer the "SIGUSR1" signal with "kill".
This will cause iroffer to jump servers to a random server from its server list. |
| SIGUSR2 |
|
If you didn't setup your config file(s) correctly and can't chat the bot there is no need to kill it and start it over again. You can initiate a "rehash" command by sending iroffer the "SIGUSR2" signal with "kill".
This will cause iroffer to re-read its config file(s) and reconfigure itself on the fly. |
| SIGTERM and SIGINT |
|
To shutdown iroffer from your shell send it a "SIGTERM" signal (the default signal when using "kill"). After the first "SIGTERM" signal, iroffer will notify xdcc transfer users of the impending shutdown, disconnect from the irc server, save the xdcc file, then exit. This can take a few seconds to complete.
If you are in a hurry, send a second "SIGTERM" signal which will cause iroffer to save its xdcc file and exit immediately. SIGINT and SIGTERM are handled the same. |
| SIGKILL |
| Do NOT use the "SIGKILL" (-9) signal, instead send two "SIGTERM"'s in a row. |
Page last modified: 09/01/04
