[tor-dev] #14995: systemd unit files - review
nusenu at openmailbox.org
Sat May 2 15:44:53 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
thanks your reply.
> This is being worked on there: https://bugs.debian.org/761403
> (which should be a more appropriate forum to discuss this topic.)
I didn't want to report bugs/feature request in debian's bts for a
non-debian repo (deb.torproject.org).
This resulted in a situation where tor's trac is apparently not
accepted by the maintainer and debian's bts is not entirely the
correct place(?) either, but with that info I'll just use debian's bts
for similar matters in the future - thanks for suggesting this and the
pointer to the current ticket.
> Please report such bugs:
> * to the Tor project's Trac if they are bugs in
> contrib/dist/tor.service.in as shipped with tor
I did so in the past but since I don't know any packages actually
using that service file shipped by tor
I'll probably just report any bugs/RFEs against the package instead of
tor itself. I hope this makes sense.
(The service file in tor does not say on which distributions it should
work and generic service file won't make use of the distribution
> * to the systemd bug tracker if they are bugs in systemd itself
If anyone is interested in systemd problems I stumble on in the tor
>> tested with jessie:
> I get a 404 there.
The file moved to a new location and has become an ansible template
(=dynamically created) instead of a static file to "improve" security
. CapabilityBoundingSet is dynamically build depending on which
capabilities are actually required (related to ). This is not
something you will be able to do in a service file that ships with a
package, but you can still copy that service file and simply remove
lines 31 and 36-39 of it .
Note: The dynamic service file adjustment I'm using is only a
temporary workaround until  gets addressed - which I don't expect
to happen in 2015.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the tor-dev