Delivery-Date: Mon, 15 Feb 2016 13:49:00 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id C20611E0A5A;
	Mon, 15 Feb 2016 13:48:58 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DF62139267;
	Mon, 15 Feb 2016 18:48:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 54C873925E
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 18:48:51 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id gGkleyt1BrbJ for <tor-talk@lists.torproject.org>;
 Mon, 15 Feb 2016 18:48:51 +0000 (UTC)
Received: from magic03.frii.com (magicmail03.frii.com [216.17.135.172])
 by eugeni.torproject.org (Postfix) with SMTP id 2542039212
 for <tor-talk@lists.torproject.org>; Mon, 15 Feb 2016 18:48:51 +0000 (UTC)
Received: (qmail 4725 invoked from network); 15 Feb 2016 18:48:46 -0000
Received: from localhost (HELO [192.168.101.125]) (cline@frii.com@127.0.0.1)
 by magic03.frii.com with SMTP
 (be63f1ee-d414-11e5-9847-3f1042aaa53a); Mon, 15 Feb 2016 11:48:46 -0700
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Pgp-Agent: GPGMail 2.5.2
From: Ken Cline <cline@frii.com>
In-Reply-To: <56C1DF24.1070009@openmailbox.org>
Date: Mon, 15 Feb 2016 11:48:45 -0700
Message-Id: <CE28579E-71E4-414D-AB4E-F58B02F3B8DE@frii.com>
References: <56C1BB18.1070703@beroal.in.ua> <56C1BF86.1050102@openmailbox.org>
 <20160215130731.GA657@riseup.net> <56C1DF24.1070009@openmailbox.org>
To: tor-talk@lists.torproject.org
X-Mailer: Apple Mail (2.2104)
X-MagicMail-OS: MagicMail 2.0-Stable
X-MagicMail-UUID: be63f1ee-d414-11e5-9847-3f1042aaa53a
X-MagicMail-Authenticated: cline@frii.com
X-MagicMail-SourceIP: 127.0.0.1
X-MagicMail-EnvelopeFrom: <cline@frii.com>
Subject: Re: [tor-talk] How to make the Tor service to stop faster?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8275443330294022484=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============8275443330294022484==
Content-Type: multipart/signed; boundary="Apple-Mail=_382EA3CE-6C06-4C95-9A63-261C1E10550C"; protocol="application/pgp-signature"; micalg=pgp-sha1


--Apple-Mail=_382EA3CE-6C06-4C95-9A63-261C1E10550C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> On 15 Feb 2016, at 7:22 AM, nusenu <nusenu@openmailbox.org> wrote:
>=20
>=20
>=20
> Pickfire:
>> Is there any reason for the ShutdownWaitLength to be 30s? That's too
>> long, no wonder it is so slow to restart the tor service.
>=20
> It is just the nicer way to say goodbye to clients - I guess.

I bet shutdown delay has to have something to do with TCP connection =
finalization semantics, which can leave client processes stuck in a =
FIN_WAIT_2 state if tor closes too quickly.  My memory is a little vague =
here, but it is a result of interrupting the FIN-> ACK<- FIN<- ACK-> =
dialogue ... the client won't close the connection until it receive's =
that last ACK form tor, which tor can't send if it closes before it gets =
the client's FIN.

I've seen this with server processes on my computer that route through =
tor.  Killing tor can leave them in that FIN_WAIT_2 state in which they =
cannot be killed, and the service cannot be restarted since the hung =
process has the service port allocated.  Then it's up to the TCP stack =
to close the connection after it times out.

So, yes - it is a nicer way to say goodbye to clients.  And nicer here =
can mean nicer to you as well.


--Apple-Mail=_382EA3CE-6C06-4C95-9A63-261C1E10550C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlbCHY0ACgkQhVEOpGWd7KBy9gCgl7WDuiMix8MQBCfrotlZ64vm
HiYAoIoDSzp7c8jp+mg2zAtd2vQl9sum
=oSoK
-----END PGP SIGNATURE-----

--Apple-Mail=_382EA3CE-6C06-4C95-9A63-261C1E10550C--

--===============8275443330294022484==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

--===============8275443330294022484==--

