chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
#ifndef SIGCHAIN_H
|
|
|
|
#define SIGCHAIN_H
|
|
|
|
|
2019-11-18 05:04:50 +08:00
|
|
|
/**
|
|
|
|
* Code often wants to set a signal handler to clean up temporary files or
|
|
|
|
* other work-in-progress when we die unexpectedly. For multiple pieces of
|
|
|
|
* code to do this without conflicting, each piece of code must remember
|
|
|
|
* the old value of the handler and restore it either when:
|
|
|
|
*
|
|
|
|
* 1. The work-in-progress is finished, and the handler is no longer
|
|
|
|
* necessary. The handler should revert to the original behavior
|
|
|
|
* (either another handler, SIG_DFL, or SIG_IGN).
|
|
|
|
*
|
|
|
|
* 2. The signal is received. We should then do our cleanup, then chain
|
|
|
|
* to the next handler (or die if it is SIG_DFL).
|
|
|
|
*
|
|
|
|
* Sigchain is a tiny library for keeping a stack of handlers. Your handler
|
|
|
|
* and installation code should look something like:
|
|
|
|
*
|
|
|
|
* ------------------------------------------
|
|
|
|
* void clean_foo_on_signal(int sig)
|
|
|
|
* {
|
|
|
|
* clean_foo();
|
|
|
|
* sigchain_pop(sig);
|
|
|
|
* raise(sig);
|
|
|
|
* }
|
|
|
|
*
|
|
|
|
* void other_func()
|
|
|
|
* {
|
|
|
|
* sigchain_push_common(clean_foo_on_signal);
|
|
|
|
* mess_up_foo();
|
|
|
|
* clean_foo();
|
|
|
|
* }
|
|
|
|
* ------------------------------------------
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Handlers are given the typedef of sigchain_fun. This is the same type
|
|
|
|
* that is given to signal() or sigaction(). It is perfectly reasonable to
|
|
|
|
* push SIG_DFL or SIG_IGN onto the stack.
|
|
|
|
*/
|
chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
typedef void (*sigchain_fun)(int);
|
|
|
|
|
2019-11-18 05:04:50 +08:00
|
|
|
/* You can sigchain_push and sigchain_pop individual signals. */
|
chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
int sigchain_push(int sig, sigchain_fun f);
|
|
|
|
int sigchain_pop(int sig);
|
|
|
|
|
2019-11-18 05:04:50 +08:00
|
|
|
/**
|
|
|
|
* push the handler onto the stack for the common signals:
|
|
|
|
* SIGINT, SIGHUP, SIGTERM, SIGQUIT and SIGPIPE.
|
|
|
|
*/
|
2009-01-22 14:03:08 +08:00
|
|
|
void sigchain_push_common(sigchain_fun f);
|
2019-11-18 05:04:50 +08:00
|
|
|
|
2015-12-16 08:04:09 +08:00
|
|
|
void sigchain_pop_common(void);
|
2009-01-22 14:03:08 +08:00
|
|
|
|
chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
#endif /* SIGCHAIN_H */
|