From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alain Schneble Newsgroups: gmane.emacs.devel Subject: Re: Asynchronous DNS Date: Tue, 2 Feb 2016 08:49:33 +0100 Message-ID: <86egcvo8ky.fsf@realize.ch> References: <87si1gx6wz.fsf@gnus.org> <86y4b5zvzt.fsf@gmail.com> <8760y9kwrk.fsf@gnus.org> <87wpqpjgwy.fsf@gnus.org> <83a8nk1cxk.fsf@gnu.org> <87h9hrnc8x.fsf@gnus.org> <86io27obqf.fsf@realize.ch> <878u331tht.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1454399443 20263 80.91.229.3 (2 Feb 2016 07:50:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Feb 2016 07:50:43 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 02 08:50:38 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aQVjO-0003jq-Sq for ged-emacs-devel@m.gmane.org; Tue, 02 Feb 2016 08:50:35 +0100 Original-Received: from localhost ([::1]:55584 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQVjO-0001td-Ed for ged-emacs-devel@m.gmane.org; Tue, 02 Feb 2016 02:50:34 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQVj9-0001tA-Ck for emacs-devel@gnu.org; Tue, 02 Feb 2016 02:50:21 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aQVj5-0000xv-Gl for emacs-devel@gnu.org; Tue, 02 Feb 2016 02:50:19 -0500 Original-Received: from clientmail.realize.ch ([46.140.89.53]:1339) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1aQViz-0000xd-MG; Tue, 02 Feb 2016 02:50:09 -0500 Original-Received: from rintintin.hq.realize.ch.lan.rit ([192.168.0.105]) by clientmail.realize.ch ; Tue, 2 Feb 2016 08:49:48 +0100 Original-Received: from MYNGB (192.168.250.224) by rintintin.hq.realize.ch.lan.rit (192.168.0.105) with Microsoft SMTP Server (TLS) id 15.0.516.32; Tue, 2 Feb 2016 08:49:30 +0100 In-Reply-To: <878u331tht.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 02 Feb 2016 18:06:22 +1100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (windows-nt) X-ClientProxiedBy: rintintin.hq.realize.ch.lan.rit (192.168.0.105) To rintintin.hq.realize.ch.lan.rit (192.168.0.105) X-detected-operating-system: by eggs.gnu.org: Windows NT kernel [generic] X-Received-From: 46.140.89.53 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:199157 Archived-At: Lars Ingebrigtsen writes: > Alain Schneble writes: > >> What happens if background thread(s) are still alive (e.g. blocking, >> waiting for a network response) and Emacs is killed? Will it wait for >> the background threads to terminate or will it forcibly kill them? > > I'm guessing they'll die along with Emacs. That's what happens with > threads started by libraries currently, I think. If so, depending on how network resources are used, it may not release them properly. They /might/ be released while the process is being stopped. But will they be released in any case? After all, it sounds a bit awkward to rely on such a behavior even if it would just work. Doesn't it?