Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-06-01 Thread Peter Palfrader
clone 816391 -1 reassign -1 systemd retitle -1 systemctl status should propagate through PartOf block 816391 -1 thanks Michael Biebl schrieb am Donnerstag, dem 14. April 2016: > Am 14.04.2016 um 00:46 schrieb Michael Biebl: > > The tor.service afaics is only used, so you have a > > systemctl resta

Processed (with 1 error): Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-06-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 816391 -1 Bug #816391 [tor] tor: "systemctl status tor" does not provide useful output Bug 816391 cloned as bug 826041 > reassign -1 systemd Bug #826041 [tor] tor: "systemctl status tor" does not provide useful output Bug reassigned from pac

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-13 Thread Daniel Kahn Gillmor
On Wed 2016-04-13 18:52:23 -0400, Michael Biebl wrote: > 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 entire

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-13 Thread Michael Biebl
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

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-13 Thread 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 o

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-13 Thread Daniel Kahn Gillmor
On Tue 2016-04-12 18:57:06 -0400, Michael Biebl wrote: > I'm missing a bit of context here. > But if you have templated services and you want to list the status for > all of them, you can use > systemctl status tor@*.service > > Is this is what you are looking for? at the moment, i see this: 0 dk

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-12 Thread Michael Biebl
Am 13.04.2016 um 00:32 schrieb Daniel Kahn Gillmor: > On Tue 2016-04-12 17:31:51 -0400, Peter Palfrader wrote: >> On Tue, 01 Mar 2016, Daniel Kahn Gillmor wrote: >> >>> Because of the systemd generator approach for tor services, i don't >>> seem to be able to do "systemctl status tor" and get any

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-12 Thread Daniel Kahn Gillmor
On Tue 2016-04-12 17:31:51 -0400, Peter Palfrader wrote: > On Tue, 01 Mar 2016, Daniel Kahn Gillmor wrote: > >> Because of the systemd generator approach for tor services, i don't >> seem to be able to do "systemctl status tor" and get any report about >> the status of the underlying services. >>