> On 23 Feb 2015, at 23:33, Nusenu <nusenu@xxxxxxxxxxxxxxx> 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. Cheers Sebastian
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk