Kaushal M <kshlmster@xxxxxxxxx> wrote: > Glusterfsd has always caught SIGTERM, SIGHUP and SIGUSR1. Right. The handling is unsafe anyway: there is no easy way to avoid races in signal handler, the only reasonable thing to do there is to set a global sig_atomic_t and handle the action outside of the signal handler. But since the goal is to exit, I guess we should be able to do something "good enough" with current code. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
