On Sun, Sep 22, 2013 at 03:33:33PM +0200, Juliusz Chroboczek wrote: > > It is a very old tradition in UNIX daemons to use the SIGHUP signal for > > exactly that reason: reload your config files and reopen your logs! > > > > This seems to be what SIGUSR2 is doing to babel, and while I can adapt > > my configuration to do that, it seems more appropriate for Babel to > > follow usual standards. > > There's a good reason for that. > > A lot of people are running babeld from the terminal. If babeld > doesn't quit at SIGHUP, they will be left with babeld processes > hanging around after they quit their session.
What about quitting on SIGHUP only if babeld is run on non-daemon mode? -- Gabriel _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
