-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Weasel,
many relay operators run multiple tor instances to overcome certain limitations. Currently the official deb packages do not come with an easy configurable way to run multiple tor instances.
I created a ticket [1] and wrote a patch [2] to add such a functionality to the debian package while preserving the current behavior.
A similar enhancement got submited to the RPM packages and is now shipped in RPMs since tor 0.2.6.4-rc [3].
It would be great if you could find some time to review and comment on #14995 - before tor 0.2.6.x gets released.
thanks! Nusenu
[1] https://trac.torproject.org/projects/tor/ticket/14995 [2] https://github.com/nusenu/tor-multi-instance-initscripts/blob/master/debian/... [3] https://trac.torproject.org/projects/tor/ticket/14996 https://lists.torproject.org/pipermail/tor-relays/2015-March/006605.html
Hi,
Nusenu wrote (16 Mar 2015 14:09:13 GMT) :
many relay operators run multiple tor instances to overcome certain limitations. Currently the official deb packages do not come with an easy configurable way to run multiple tor instances.
Just for the record, we've discussed this a few months ago with weasel, and the plan was to use a systemd unit template, that allows to support this feature in a nice and elegant way:
* introductory blog post about it: http://0pointer.de/blog/projects/instances.html * http://www.freedesktop.org/software/systemd/man/systemd.unit.html (look for "unit template")
I've no opinion regarding adding such support to the SysV initscript, except I'm not personally interested in working on it myself (contrary to the systemd-based solution).
Cheers, -- intrigeri
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
intrigeri:
Nusenu wrote (16 Mar 2015 14:09:13 GMT) :
many relay operators run multiple tor instances to overcome certain limitations. Currently the official deb packages do not come with an easy configurable way to run multiple tor instances.
Just for the record, we've discussed this a few months ago with
Is there a trac entry?
weasel, and the plan was to use a systemd unit template, that allows to support this feature in a nice and elegant way:
Yes, that is great because I actually prefer systemd's way to do this as well :)
I'll prepare a unit file for this and add it to the trac entry.
Weasel wrote:
Tor trac is not the place to discuss Debian packaging enhancements
Even if we are talking about the debian packages provided by the torproject? https://deb.torproject.org/torproject.org/dists/
Nusenu wrote (17 Mar 2015 12:15:22 GMT) :
intrigeri:
Just for the record, we've discussed this a few months ago with
Is there a trac entry?
I don't think so.
I'll prepare a unit file for this and add it to the trac entry.
\o/
Weasel wrote:
Tor trac is not the place to discuss Debian packaging enhancements
Right. In the specific case of systemd unit templates, I think that a great part of the work will have to be done upstream first, before the Debian packaging can take benefit of it, so perhaps Tor's Trac is appropriate for the time being. Unless we want to support systemd unit templates only in Debian, but that would be a bit sad.
Cheers, -- intrigeri
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
I'll prepare a unit file for this and add it to the trac entry.
a first version is there
https://bugs.torproject.org/14995
Weasel wrote:
Tor trac is not the place to discuss Debian packaging enhancements
Right. In the specific case of systemd unit templates, I think that a great part of the work will have to be done upstream first, before the Debian packaging can take benefit of it, so perhaps Tor's Trac is appropriate for the time being. Unless we want to support systemd unit templates only in Debian, but that would be a bit sad.
I mainly aimed for Debian since Ondrej stated he wont migrate RPM packages to systemd anytime soon, but I would be happy to prepare unit files for RPM as well if there is a chance to get them into the RPM packages.