Delivery-Date: Mon, 23 Feb 2015 17:34:01 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,URIBL_BLOCKED
	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 DF1631E02F0
	for <archiver@seul.org>; Mon, 23 Feb 2015 17:33:59 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8C9C932C59;
	Mon, 23 Feb 2015 22:33:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 034C732156
 for <tor-talk@lists.torproject.org>; Mon, 23 Feb 2015 22:33:52 +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 OZEBbg4ylvby for <tor-talk@lists.torproject.org>;
 Mon, 23 Feb 2015 22:33:51 +0000 (UTC)
Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id C6D2030087
 for <tor-talk@lists.torproject.org>; Mon, 23 Feb 2015 22:33:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail2.openmailbox.org (Postfix) with ESMTP id 568272000BD
 for <tor-talk@lists.torproject.org>; Mon, 23 Feb 2015 23:33:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openmailbox.org;
 h=content-transfer-encoding:content-type:content-type:subject
 :subject:mime-version:from:from:date:date:message-id:received;
 s=openmailbox; t=1424730826; bh=Dx1tOnVCOlZQWKIGQgdS0+DAUoK846w
 T1ETPHHAY7f0=; b=iQ16vRJKBAe0Wen06DIk+tu4qULOWYefk69GK23qO88kF3N
 EWe8ayxGGsrqYebsf8NsHy5detKJ6XeS70IGHeFh8z85xhL+gxfV8Yx+gWx0ETZJ
 Qoww5KhMfUSL37MwqgXYs2y7BWn/Z0SwhnRwqBHE281oJ4dCRkO19SThEf9I=
X-Virus-Scanned: amavisd-new at openmailbox.org
Received: from mail2.openmailbox.org ([62.4.1.33])
 by localhost (mail.openmailbox.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id KTnoMgvCsetY for <tor-talk@lists.torproject.org>;
 Mon, 23 Feb 2015 23:33:46 +0100 (CET)
Message-ID: <54EBAAC6.8040901@openmailbox.org>
Date: Mon, 23 Feb 2015 22:33:42 +0000
From: Nusenu <nusenu@openmailbox.org>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
Subject: [tor-talk] tor --verify-config opens listeners? (for short
	timeframe)
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I stumpled on this while debugging an ansible role.

It basically does this:
tor --verify-config -f foo.torrc
tor -f foo.torrc

while the torrc is fine and the first tor execution retuns 0 the
second one will *sometimes* fail (depends on exact timing) because
'tor --verify-config' apparently occupies the ports - so the second
tor invocation can't start anymore because the ports are still in use.

same problem with (I didn't expect that):
tor --verify-config -f foo.torrc && tor -f foo.torrc

If you want to reproduce it you might have to try few times till it
fails (and don't forget to kill tor when it didn't fail).

If this is expected behaviour please update the manual page to include
information that --verify-config actually does quiet a bit more than
reading the configuration file :)


thanks,
Nusenu
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJU66rGAAoJEFv7XvVCELh0vIUQAKjWiPD4nptastyVBQzcM+ho
K8fJrvH8ADiEVsHr2Zp+KDdx8jZCUFLmpQFn3qiUd5UTOgjEjo5AFr2/GsQLI5ro
HEKoPIZcYw50Qx8UYabnc8AjUFLiVWsTGgGYD5gjdrmmUSA6OILRW1z7fpXH4pwV
JN1w/LKCZj6O0Y47jzsuDsqMSib28LXLHCzmBU8TXOhxN3/BYrW8VRE+F313Fr5C
eVQqyjMr9vHB3C6UEPQskOCW1QvFMrLHYs/J4uY09DYzkYjt0svyvRKdk+nhYRA0
X71gSz9iasF0pJXUhY4FvYPNN41ii8d1Y5l7+A1lrUEppm49rIAUMIsF3xZPVM0m
u1gY0ZItLX0e7q8LutllE6E4Zsqv4MWzOj6HRRcs4CRl3Via2TJ9g+i7FliNkVo0
TvWYNdiaq4cSjZ19gX4ybMvi5tnQeueVCG/lk5RbRcib7LNx7Br0DdZz+vePdinH
7n5hIEVJ8c1L/DfsG1yEFt48Fnzi6d2bnwgNj+z0bRoYL0gzMbrLZ9Mj8uV6iZMj
d5bxNARCSQGX9SHAXDAT3H+Jb0kHrOZskFB3bG/q62q0W0JNnNnL/nAt263CAQ8B
Qch5CVefeu2UyYsrfiqgZtDjNHfNkmIOgCsY2sg7z5/FhZ4SBfGPMcX1WXOjPAr+
ksINd7MVH795Utp7VPd6
=BA5u
-----END PGP SIGNATURE-----
-- 
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

