Revision 2d6bdcc5 man/hbal.rst
| b/man/hbal.rst | ||
|---|---|---|
| 400 | 400 |
|
| 401 | 401 |
- by sending a ``SIGINT`` (``^C``), hbal will register the termination |
| 402 | 402 |
request, and will wait until the currently submitted jobs finish, at |
| 403 |
which point it will exit (with exit code 1) |
|
| 403 |
which point it will exit (with exit code 0 if all jobs finished |
|
| 404 |
correctly, otherwise with exit code 1 as usual) |
|
| 405 |
|
|
| 404 | 406 |
- by sending a ``SIGTERM``, hbal will immediately exit (with exit code |
| 405 |
2); it is the responsibility of the user to follow up with Ganeti the
|
|
| 406 |
result of the currently-executing jobs |
|
| 407 |
2\); it is the responsibility of the user to follow up with Ganeti
|
|
| 408 |
and check the result of the currently-executing jobs
|
|
| 407 | 409 |
|
| 408 | 410 |
Note that in any situation, it's perfectly safe to kill hbal, either via |
| 409 | 411 |
the above signals or via any other signal (e.g. ``SIGQUIT``, |
| 410 | 412 |
``SIGKILL``), since the jobs themselves are processed by Ganeti whereas |
| 411 | 413 |
hbal (after submission) only watches their progression. In this case, |
| 412 |
the use will again have to query Ganeti for job results.
|
|
| 414 |
the user will have to query Ganeti for job results.
|
|
| 413 | 415 |
|
| 414 | 416 |
EXIT STATUS |
| 415 | 417 |
----------- |
Also available in: Unified diff