Glusterfsd has always caught SIGTERM, SIGHUP and SIGUSR1. SIGTERM for cleaning up and exiting
SIGHUP for reloading configuration (although AFAIU it's used for rotating logs) SIGUSR1 for statedump. On Thu, Apr 16, 2015 at 8:40 PM, Emmanuel Dreyfus <m...@netbsd.org> wrote: > On Thu, Apr 16, 2015 at 07:52:49PM +0530, Kaushal M wrote: >> Because this GlusterD didn't die > > Um, that is something I have been seeing on netbsd-6: killing glusterd does > not cause it to exit, you have to kill -9. On netbsd-7 it is fine. > > The question is therefore: why does it catch SIGTERM? > > -- > Emmanuel Dreyfus > m...@netbsd.org _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
