[tor-talk] tor --verify-config opens listeners? (for short timeframe)

Sebastian Hahn sebastian at torproject.org
Mon Feb 23 23:07:17 UTC 2015

> On 23 Feb 2015, at 23:33, Nusenu <nusenu at openmailbox.org> wrote:
> 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 :)

This is a bug. Feel free to file it and assign it to me  (Sebastian
on trac.torproject.org), I'll take care of it in a few days.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20150224/da303550/attachment.sig>

More information about the tor-talk mailing list