# Window-close not killing everything

**URL:** <https://www.ruby-forum.com/t/window-close-not-killing-everything/234773>\
**Category:** GNU Radio\
**Created:** [May 23, 2014, 7:15pm UTC](https://www.ruby-forum.com/t/window-close-not-killing-everything/234773 "2014-05-23T19:15:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [May 23, 2014, 7:15pm UTC](https://www.ruby-forum.com/t/window-close-not-killing-everything/234773/1 "2014-05-23T19:15:29Z")

</div>

I have a user of “simple\_ra” that has an issue with pieces of it still  
running after they use the “window close” button. In particular,  
there’s an XMLRPC  
server thread that gets left behind. On my own, Fedora 14, system  
here, it’s not a problem. Window close kills everything. On his Ubuntu  
12.04  
system, it seems to kill off most of it, but there’s this dangler  
that is holding the XMLRPC socket.

If I bind a “close” button to a function that issue a signal-to-self,  
what signal should that be? SIGHUP?

–  
Marcus L.  
Principal Investigator  
Shirleys Bay Radio Astronomy Consortium

> **[Live Draw HK Tercepat | Result HK | HK Pools | Live HK | HK Prize Hari Ini](https://www.sbrac.org/)**
>
> Temukan live draw hk tercepat melalui halaman hk pools yang resmi dan dapatkan result hk prize melalui live hk secara langsung di situs kami.