-----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
