[tor-dev] multi-instance tor with a single torrc

[Nusenu]

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

Hi Pascal,
(OpenBSD tor package maintainer)

(splitting this part off to tor-dev, since it is not suited well for
tor-relays I guess)

For the interested reader this discussion started here [1].

Pascal Stumpf:
>> Multi-instance support isn't something that's provided by
>> OpenBSD's rc.d(8) subsystem, and I doubt it ever will be.  Too
>> much complexity for something that's more of a crutch to work
>> around few applications' limitations than something universally
>> needed and useful.
> 
>> I think the real solution would be to talk to upstream about
>> improving MP scalability.  Even if it's just something as
>> primitive as forking a child for every ORPort directive in
>> /etc/tor/torrc, it would be much easier than having to keep track
>> of a bazillion individually started tor instances, all with their
>> own configuration files.

I guess this (forking one tor instance per ORPort line) sounds a lot
simpler than it actually would be. How do you handle ControlPort, HS,
DataDir, ExitPolicy and basically any other config option, ...

but since I need a solution in the near future I'll probably just go
with multiple services on OpenBSD.

thanks,
Nusenu




[1]
https://lists.torproject.org/pipermail/tor-relays/2015-April/006741.html
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVHuIaAAoJEFv7XvVCELh03H0QAKpg05vfOS/DTJ6Qhl7TfQV/
pKiAHjVfbWOfBD4vfqMHX0H054l7WfRUUiSz6gZ9DRGwXj7uDXh59kjsNa2ipMvK
4YYvDXjUIh3UBZdDnjLrkRPI5Lws1PuCi6wvnFX+e/weWiWQ18N/2HALaluhyldI
3aiDWA3k0ZnZVkuLLpbkxvbol8HS0upMTkwWlba/QXdWflK3it6sydkIi8EMhMx4
cEfTRCvWjxxU5YguIQ7/NpNFpKvRCtUEoCKBLjXuUGKTvawQ+Xu+XJQeSqE/yOqO
Z1lTSQqH4i7JjBGEMxXQP/U7B3gELxv2tRcpfImGQZArLim41VPTVXse2+dPhb4d
0Knl19yYxtd4gjtoMbnv3GEPNgj2xnBr8e2MEYDsRY+rGYFnHEtnPvmJmC5p/vtX
NAcuReFLd+y3j2PuB0XJHlGYOLtzvtaXJdiqV6oq42Mu0VHpiGfbTfKi2k8ZMUTw
PfLQjx9z3dQ6GleC1mGHdMeJ7bJ7Wk2dJ7dicLF0veY5/Gc7gkYtWibsLXggTwrQ
K0IqXnGJ8fWM41ZO4hhpmkkywhXodLzlWlXCxgxDUBsuFci/mVvtfu6ylxh+LCqG
y5TxIk1T4/i+atx7jvuMLgrZGf02YgFyCf15Swj+VoDxx8GAxJl9nEQx0jD5d+Zl
206/+0QAI5hksaedorvj
=qUCf
-----END PGP SIGNATURE-----