# SIGWINCH & aborting, a cleaner solution?

**URL:** <https://www.ruby-forum.com/t/sigwinch-aborting-a-cleaner-solution/210824>\
**Category:** NGINX\
**Created:** [August 18, 2011, 10:39am UTC](https://www.ruby-forum.com/t/sigwinch-aborting-a-cleaner-solution/210824 "2011-08-18T10:39:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [August 18, 2011, 10:39am UTC](https://www.ruby-forum.com/t/sigwinch-aborting-a-cleaner-solution/210824/1 "2011-08-18T10:39:17Z")

</div>

Hello,

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 S., that he advised to modify the  
source code and deactivate the  
handling[http://forum.nginx.org/read.php?2,6771](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  
this issue.

Does somebody have solution that does not include patching?

Thank you.

---

<div class="post-metadata">

**Author:** ![SSFSSlix\_DelvalSS\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/dfb087/32.png) [@SSFSSlix\_DelvalSS\_S](https://www.ruby-forum.com/u/SSFSSlix_DelvalSS_S)\
**Post date:** [August 18, 2011, 10:42am UTC](https://www.ruby-forum.com/t/sigwinch-aborting-a-cleaner-solution/210824/2 "2011-08-18T10:42:59Z")

</div>

On Thu, Aug 18, 2011 at 10:29:40AM +0200, Flix Delval wrote:

> 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  
> this issue.
> 
> Does somebody have solution that does not include patching?

Do you run with “daemon off” only or with master\_process off" too ?  
I think SIGWINCH should just be disabled in non-daemon mode.

–  
Igor S.

---

<div class="post-metadata">

**Author:** ![SSFSSlix\_DelvalSS\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/dfb087/32.png) [@SSFSSlix\_DelvalSS\_S](https://www.ruby-forum.com/u/SSFSSlix_DelvalSS_S)\
**Post date:** [August 18, 2011, 4:43pm UTC](https://www.ruby-forum.com/t/sigwinch-aborting-a-cleaner-solution/210824/3 "2011-08-18T16:43:56Z")

</div>

On Thu, Aug 18, 2011 at 10:29 AM, Flix Delval  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)wrote:

> this issue.
> 
> Does somebody have solution that does not include patching?
> 
> Do you run with “daemon off” only or with master\_process off" too ? I think  
> SIGWINCH should just be disabled in non-daemon mode.

I only had ‘deamon off’, adding ‘master\_process off’ solved my issue. I  
didn’t know what that parameter was doing exactly.

I will communicate the result.

Thank you very much.