Re: Signal handling in current CVS

2010-05-16 Thread Nicholas Marriott
Sorry for the delay, this is applied now, thanks. On Sat, May 15, 2010 at 12:03:03AM +0200, Romain Francoise wrote: > I see that my patch is now in CVS, thanks! But the merge from > OpenBSD back to SF was a bit careless, the setenv/unsetenv > configuration for libevent is now a no-op since event_

Re: Signal handling in current CVS

2010-05-14 Thread Romain Francoise
I see that my patch is now in CVS, thanks! But the merge from OpenBSD back to SF was a bit careless, the setenv/unsetenv configuration for libevent is now a no-op since event_init() was moved elsewhere... please apply the following to SF to restore it: Index: server.c =

Re: Signal handling in current CVS

2010-04-28 Thread Romain Francoise
Nicholas Marriott writes: > I wonder if to make it nicer we could unify the signal set > functions into one set_signals(void (*)(int, short, void *)). And > similarly could have one clear_signals function. > All the processes could ignore SIGINT, SIGPIPE, SIGUSR2, SIGTSTP, > SIGHUP, and all catc

Re: Signal handling in current CVS

2010-04-28 Thread Nicholas Marriott
I wonder if to make it nicer we could unify the signal set functions into one set_signals(void (*)(int, short, void *)). And similarly could have one clear_signals function. All the processes could ignore SIGINT, SIGPIPE, SIGUSR2, SIGTSTP, SIGHUP, and all catch SIGCONT, SIGTERM, SIGWINCH, SIGCHLD,

Signal handling in current CVS

2010-04-27 Thread Romain Francoise
The last change in tmux.c to ignore SIGCHLD in main() introduces a bug: the signal handler is never reset back to SIG_DFL and this signal configuration in inherited by the server when it's created, and in turn by the commands that are spawned because signal_del() resets it to the previous value in