SIGWINCH & aborting, a cleaner solution?
felixdelval at gmail.com
Thu Aug 18 08:29:40 UTC 2011
I am using nginx in a terminal as development server, not as a daemon.
Each time nginx receives the SIGWINCH signals, it says : 2011/08/18 10:12:54
[alert] 12887#0: aborting
I have seen in a email from Igor Sysoev, that he advised to modify the
source code and deactivate the
handling<http://forum.nginx.org/read.php?2,6771>of the signal there.
It works fine, but it doesn't seem to me as long-term
reliable solution. I know I am not the only one who has been asking about
Does somebody have solution that does not include patching?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx