Bug#816391: tor: "systemctl status tor" does not provide useful output
email at michaelbiebl.de
Wed Apr 13 23:52:23 BST 2016
Am 14.04.2016 um 00:46 schrieb Michael Biebl:
> Am 13.04.2016 um 21:45 schrieb Daniel Kahn Gillmor:
>> is there a reason to have a "tor.service" that is distinct from the
>> tor@*.service files? if not, maybe we could get rid of it entirely?
>> If there is a reason to have it, how can we avoid having "systemctl
>> status tor" mask the statuses of the actual running (or failing)
> The tor.service afaics is only used, so you have a
> systemctl restart/reload tor
> shortcut which propagates that request to all instances.
> tor.service in itself does not provide any service.
> So it is useful to have.
I'm not sure. Maybe we can convince upstream that using "status" on a
service which is composed by several sub-services via PartOf , also
propagates the status request and merges that into a single output.
Or we add a dedicated key, like PropagatesReloadTo , say ProgatesStatusTo
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers